Also, if you remove the configuration entry, it doesn't work either.
-Original Message-
From: Fong Tsui
Sent: Wednesday, November 21, 2007 12:12 PM
To: Fong Tsui; '[email protected]'
Subject: RE: SIGHUP
I found that it doesn't work if you add the comments in front of
I found that it doesn't work if you add the comments in front of the
configuration entry. But if you really change the configuration entry,
it works fine.
-Original Message-
From: Fong Tsui
Sent: Wednesday, November 21, 2007 12:06 PM
To: [email protected]
Subject: SIGH
Hi, everybody,
I am trying to use "SIGUP" to re-load the configuration instead of
restarting snmpd. It seems some of configuration is reloaded correctly
but some of them are not.
When I comment out rocommunity entry in snmpd.conf and do "killall -HUP
snmpd", I can see log message:
snmpd[6458]:
On 21/11/2007, Younger Wang <[EMAIL PROTECTED]> wrote:
> Run the command:
> Snmpgetnext -v 1 -c
> SNMP-VIEW-BASED-ACM-MIB::vacmSecurityModel.0."wes"
> SNMP-VIEW-BASED-ACM-MIB::vacmSecurityModel.0.wes:
> (Index out of range: 0 (vacmS ecurityModel))
> Get-Next was never sen
Run the command:
Snmpgetnext -v 1 -c
SNMP-VIEW-BASED-ACM-MIB::vacmSecurityModel.0."wes"
SNMP-VIEW-BASED-ACM-MIB::vacmSecurityModel.0.wes: (Index out of range: 0
(vacmS ecurityModel))
Get-Next was never sent out, because it found 0 invalid according to the MIB.
BR
Younger Wang
-Or
