> The other option would be if the agent was running as a > non-privileged process, so couldn't open (privileged) port 161. > But if you're starting things as root, then that's less likely. > > I'd check for the presence of another SNMP agent.
A useful tip - if you find you can't attach to a given port is to run lsof -i -P and see what processes have which ports in use... (Or run a netstat -a | more and see what netstat thinks is open). -- Richard Horton Users are like a virus: Each causing a thousand tiny crises until the host finally dies. http://www.solstans.co.uk - Solstans Japanese Bobtails and Norwegian Forest Cats http://www.pbase.com/arimus - My online photogallery ------------------------------------------------------------------------- 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-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
