edirmon is a tool designed to provide nwmon.nlm functionality for eDirectory on linux. It collects information, evaluates eDirectory health based on the information, and places the information in its data logs.
edirmon can be run in interactive mode (with a screen showing data and health) or in daemon mode where it only logs information and health. The data logs are placed in the configured edirmon data directory. Program information and changes in health are sent to the system logger for processing. You can also optionally create an html health screen (edirmon does not contain a web server).
edirmon mimics nwmon in functionality and output.
Installation and Configuration
Install the RPM.
edirmon can pretty much run out of the box if eDirectory is installed using the default paths. The only setup that has to occur after installing the rpm is supplying credentials to use when pulling iMonitor data in /etc/opt/novell/edirmon/conf/secret. You may also want to make changes to /etc/opt/novell/edirmon/conf/edirmon.conf, depending on your setup.
All program information is sent to the system logger for processing, so it is possible for the sysadmin to route information based on the syslog configuration. This allows edirmon to integrate with existing infrastructure for centralized logging or alerting.
All messages are sent as LOG_USER facility. Program debug messages are LOG_DEBUG level. Health status changes to HEALTHY are LOG_INFO level. Health status changes to SUSPECT are LOG_WARNING level. Health status changes to UNHEALTHY are LOG_ERR level.
OES2SP2 now uses /opt/novell/eDirectory/sbin/post_ndsd_* /etc/init.d/ndsd has a section for migrating them out of /etc/init.d (where they should not have been in the first place, IMHO).
might want to update your README
Also, to avoid the "openvt: vt 8 is in use; command aborted, use `openvt -f' to force." should we stop and start the edirmon daemon too ?? or do you recommend to leave it in memory during ndsd restarts ???
this could be enabled by using the operating system's mail command (/usr/bin/mail in SLES) and perl's system command.
so cat /tmp/file/.txt | mail -s "the subject" firstname.lastname@example.org -r email@example.com
should be acceptable to many if you have a template for the format of the email, people can fiddle with the format to their hearts content, just provided they leave your variables in place. shouldn't be too much work (honest !!!)
eg : to replace the server name sed -i "s:SERVER_NAME/$HOSTNAME/g" /tmp/file.txt might be all that is needed to put the server's name into the template file prior to sending the alert. There is probably a more suitable perl way of doing it.
I think a lot of people need this - and I am too 'limited' :-) to find the attachment on the coolsolution if it is there. Otherwise I would suggest to up the version count and publish the version built without using lsLzma.
Sorry about the IsLzma issue - that was a function of my build host being SLES11 and not a requirement of the rpm. I just repackaged it on a SLES9 host and attached a version which should fix these issues.