Hi Alex,

I just became aware of snmptt, looks nifty, but of course I have some patches 
and comments, even though I haven't actually used it too much at all yet :).  
Let me know what you think and if you'd rather have me file these in sf.net 
tracker.

All of the stuff below was with snmptt 1.2 running on CentOS 5, with pretty 
much the default .ini configuration from the tarball.

First, two patches:

- snmptt-init.patch adds LSB init keywords and actions to the init script, and 
makes snmptt start earlier and shutdown later than snmptrapd (which is 50, 50 
at least on Fedora and CentOS).

- snmptt-logdir.patch changes default log dir and examples to point to 
/var/log/snmptt instead of /var/log because it is easier to arrange write 
access to the former for non-root (snmptt) user than the latter.

Attached is also a logrotate file for the snmptt daemon.  Which brings me to 
the remaining comments:

- It'd be nice if snmptt closed and reopened debug file handles on HUP in 
addition to reloading configuration; that way for example the logrotate 
scriptlet could just do a HUP instead of a full restart which I think would be 
a bit cleaner and follow what I think daemon processes usually do.

- I see that log files end up created as world writable, which smells like a 
security issue to me.  I suppose this is because of the "umask 0"s in the 
code.  Isn't there a way to have the non-root user remain able to write to the 
logfiles without making them world writable?

- It would be nice to have a command line option for turning on 
net_snmp_perl_enable - that way it could be easily enabled for daemon 
processes while (if the default is disabled) the non-daemon mode would have it 
disabled by default.

- When starting up in daemon mode, I see this in syslog "snmptt-sys[0]: Could 
not open debug output file!" even though I have not requested any debugging at 
all.  Would be nice to get rid of this warning or to improve its wording 
(confusing when I haven't requested anything debug related as far as I can 
tell) as well as to have the filename and actual error message included in the 
message.

- I'd prefer daemon mode to be quiet wrt. stdout; now it spews things like 
"Config file /etc/snmp/snmptt.ini loaded", "/var/run/snmptt.pid", and "cwd: 
/etc/logrotate.d" on startup.

Thanks for snmptt and your time, Ville