Thanks Dave,but I forgot to say that this is only a test of the real
environment.The snmp daemon is only a part of a complete application. Of course
when the application is shut-down we use kill -TERM to stop the snmpd. The
problem is when the termination of the application is not controlled by any
problem (which is not very frequent, but possible). That's why we need to dump
the data on real-time
> Date: Thu, 17 Nov 2011 08:52:32 +0000
> Subject: Re: Persistent data not saved at runtime
> From: [email protected]
> To: [email protected]
> CC: [email protected]
>
> On 17 November 2011 08:42, Miguel Toledano Ortega <[email protected]>
> wrote:
> > From this point there are two cases:
> > 1) If I stop the snmpd in a controlled way and then restart it,
> > the password is the expected one ("passwd_new")
> > 2) If the snmpd is killed (kill -9, Ctrl+C...) and then restart it,
> > the password comes back to the previous one ("passwd_old")
>
>
> > Does anyone know anyway to avoid this issue
>
> Don't use "kill -9" ! Use "kill -TERM" instead.
>
> kill -9 is a mechanism of last resport, and should *NOT* be used
> as a matter of course.
> Any lazy administrator who habitually forces programs to quit
> abnormally deserves everything they get!
>
> (I'm a little more worried about Ctrl+C - that ought to shut down
> cleanly, and hence save the password change)
>
>
> Dave
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
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
