Limph / News: Recent posts

Added host agents to monitor disk space and/or *nix system load and send it back to the limph installation encrypted.

1.8.2
Fixed major poller forking/db connection bug.
All users encouraged to upgrade.

1.8.1
Fixed UDP false positive bug.
Added option to truncate hostnames in host discovery, the new default.

1.8
Added login-free status screen.
Added subnetted host discovery, bulk discovered host addition.

1.7
Added portscanning tool to host_add, host_edit.
Fixed SQLite/PDO password change function.

1.6.1
Added SQLite/PDO support. Warning: Password change does not work. Can be worked around using user creation/deletion.

Now with experimental and untested SQLite support. SQLite support in PHP does not work in all configurations and versions, so YMMV. Please make sure your PHP install supports SQLite before submitting a bug report.

Added MySQL 3.23 compatibility. Helpful mostly for new installs. Existing users need not upgrade.

Limph now supports PostgreSQL. This is in no way indicative of my feelings towards MySQL, simply a desire to make Limph available to PostgreSQL users. This is my first experience with PostgreSQL, so if you have any trouble at all, please submit your issue to the supoprt forums to I can correct the issue ASAP. Thank you!

This release fixes a bug in which the poller echos all checked hostnames. On some systems, this will cause cron to gradually fill the mail box of account running the poller.

This release is primarily focused on hierarchical checks. Hosts can be organised into a dependancy tree, or not, depending on the wishes of the user. Hosts depending on a Down host will not be polled, and will be marked Unreachable on the display. History data is still only kept on hosts that are confirmed Up or Down. Looks like Limph is at or past the most commonly used features of Node Runner.

Fixes the aforementioned ID change bug.

Do not alter user IDs. If you do, your login will not work. A bugfix release correcting this will be out soon. Sorry for the inconvenience. You may still alter attributes of user IDs, such as notification settings, but not the ID itself. If you do this and manage to log out before changing it back, you may restore the ID through a direct database edit. The value you need to change is in the table USERS, and the field is ID.

Basic feature set, described above. See online Changelog for install instructions.