>>>>> "RS" == Robert Story <[EMAIL PROTECTED]> writes:
RS> Actually, after looking at the code, the closing of the pipe/fd is RS> a signal to the persist app, which should terminate on that RS> condition. Thus, I think this is a bug in the persist script, not RS> the agent. The reason, IMHO, for considering the patch is not because it's perfect (I agree it'd be better to do better cleanup during a HUP including a potential "notify" followed by a "sleep/wait" followed by actual dealing with things; but that's a MAJOR rewrite of a huge amount of code unless you do a notify/sleep/wait per potential open sub-thingy which would be a very slow HUP handle)... The reason for the TERM signal is that without it the agent hangs. IE, the agent is protecting itself from one script causing a complete hang of the whole system. Certainly you could classify it as a bug in the script, but robust programming would still have you protect yourself from others. I'm actually only just over the fence about whether it should go into 5.4. But I'm over it none the less, because the case is rare and doing a blocking wait on a PID that will never exit seems broken. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders