Hello, when the snmpd fails to bind listening port, it writes 'Error opening specified endpoint "udp:0.0.0.0:162", Server Exiting with code 1' to syslog and dies, but its exit code it 0.
I looked into the sources and I can see that the agent is deamonized before the listening sockets are created. Is there any specific reason for this? Wouldn't it be better to bind the listening ports and deamonize (i.e. fork) afterwards, when we know that everything works? I'd volunteer to fix this, but I do not know if there is some pitfall I do not know about. 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
