a) It successfully creates the socket.
b) The agent does 'connect', but fails to register. Note netstat's
output for the sub-agent app 'rmApps-subDemo' for when the master
agent and sub-agent are connected. (see below)

After shutting down the sub-agent and master agent, the socket
'master' does not delete. However, i would like to note, when using
tcp sockets, the socket no longer exists.

Raul

unix  3      [ ]         STREAM     CONNECTED     402710 7539/rmApps-subDemo 
tcp        0      0 *:smux                      *:*                   
     LISTEN      7538/snmpd
udp        0      0 *:snmp                      *:*                   
                 7538/snmpd
unix  2      [ ACC ]     STREAM     LISTENING     402646 7538/snmpd   
      /var/agentx/master
unix  3      [ ]         STREAM     CONNECTED     404369 7538/snmpd   
      /var/agentx/master




On 4/29/05, Dave Shield <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-04-29 at 14:23, W Raul S wrote:
> >  The socket is created when the master agent starts up. It is not
> > deleted (as usual) when the master agent shutsdown.
> 
> That's what I half suspected.  Normally the master agent *should*
> delete the socket when it closes down cleanly (I think).
> 
> What happens if you shut down the master agent, explicitly delete
> the named socket, then start the master agent up again?
> 
>  a)  Does it successfully create /var/agentx/master ?
>  b)  If so, can the subagent now connect to it?
> 
> Dave
> 
>


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id5hix
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to