Wes Hardaker wrote: >>>>>> On Tue, 11 Nov 2008 15:43:24 +0100, Jan Safranek <[EMAIL PROTECTED]> >>>>>> said: > > JS> I looked into the sources and I can see that the agent is deamonized > JS> before the listening sockets are created. Is there any specific reason > JS> for this? Wouldn't it be better to bind the listening ports and > JS> deamonize (i.e. fork) afterwards, when we know that everything works? > > JS> I'd volunteer to fix this, but I do not know if there is some pitfall I > JS> do not know about. > > As I mentioned on IRC, it sounds like the right "thing to do" (TM) to me.
I moved the forking after transport creation in trunk (SVN #17313). I'd port it back to 5.4 branch if nothing breaks for few weeks or months. Jan ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
