Putting the question in other way.

As I said magt uses tcp/199 port and snmpd also tries
to bind tcp/199 port, the following  error comes in
snmpd.log but snmpd starts and works fine
"[init_smux] bind failed: Address already in use"
I  like to know is it a warning or an serious error.
What are the problems it will create for this error.?

Any help will be great.

Thanks & regards
Mamon


--- mahua dutta <[EMAIL PROTECTED]> wrote:

> Hi,
> I am facing one problem . I have already one smux
> peer
> agent. Master agent(magt) uses the 199 port.
> 
> Net-snmp( version net-snmp-5.2.1) in linux also uses
> the 199 port . So it is mutually exclusive. I can
> run
> one of them.
> 
> But I need to run both. I saw some help in this
> mailing list. The link is as below.
>
http://sourceforge.net/mailarchive/message.php?msg_id=9848810
> 
> Using this I can run the magt in different port and
> the magt smux have 199/TCP... port.
> But the next part in that article smuxsocket
> 1.0.0.0,
> if i provide in snmpd.conf file , it gives 
> "/etc/snmp/snmpd.conf: line 56: Warning: Unknown
> token: smuxsocket." while running snmpd.
> 
> Please help me in this regard.
> 
> 
> 
> 
>               
> __________________________________ 
> Yahoo! Mail 
> Stay connected, organized, and protected. Take the
> tour: 
> http://tour.mail.yahoo.com/mailtour.html 
> 
> 



                
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to