Hi list,
I believe there is a bug in the daemonize code of ipmievd. While trying
to run ipmievd on one of our Solaris 9 servers, I found that the daemon
is running, but that it's not logging to syslog. I start the daemon with:
ipmievd -H <hostname> -I lan -U <username> -P <password> sel daemon
After a couple of hours debugging, I found why it's not logging. In
lib/helper.c, line 401, I found:
for (fd=0; fd<64; fd++)
close(fd);
I am not a programmer, but this looks a bit odd to me. 64 file
descriptors are being closed, including the one of the socket which is
needed to write to syslog.
These should be closed before the call to openlog(), but I have not tested the ipmievd syslog interface on solaris in a long time so it may be that closing all the open filehandles is harmful to future syslog() use. I'
Deleting the lines above gives me a working daemon, so I am all happy,
but I would like to know why these file descriptors are being closed.
I've a little feature request as well: it would be nice to see the
hostname of the polled device in the log. When running multiple daemons
which all log to LOG_LOCAL4, it's hard to see which device has problems.
That is a reasonable request that I'll put in for 1.8.9. One message of 'CPU0 Over Temperature' could be confusing if you are watching 10 systems...
-duncan
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
