On Tue, 28 Jun 2005 19:35:36 +0100 Kevin wrote:
KC> According to the man page for "snmptrapd" I should be able to force it
KC> to re-open its log file via a SIGHUP signal. Unfortunately it doesn't work.
KC>
KC> EG, if I have "snmptrapd -Lf /var/log/snmptrapd.log" the file is
KC> created OK but if I then move snmptrapd.log to snmptrapd.log.1 and
KC> "kill -SIGHUP <pid_snmptrapd>" no new "snmptrapd.log" is created, it
KC> just keeps writing to snmptrapd.log.1 (presumably because the inode
KC> doesn't change)
Hmm.. looking at the code for 5.1.2, it looks like it should work. Do you see
the "NET-SNMP version %s Reconfigured" message in the .1 logfile?
If you can run under a debugger, set a breakpoint in snmp_enable_filelog(). It
should close, then re-open the file.
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
unless they are requests for paid consulting services.
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
