

<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://www.net-snmp.org/wiki/index.php?action=history&amp;feed=atom&amp;title=Persistent_Storage_Does_Not_Get_Updated_Immediately</id>
		<title>Persistent Storage Does Not Get Updated Immediately - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://www.net-snmp.org/wiki/index.php?action=history&amp;feed=atom&amp;title=Persistent_Storage_Does_Not_Get_Updated_Immediately"/>
		<link rel="alternate" type="text/html" href="http://www.net-snmp.org/wiki/index.php?title=Persistent_Storage_Does_Not_Get_Updated_Immediately&amp;action=history"/>
		<updated>2026-05-05T05:27:41Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.26.3</generator>

	<entry>
		<id>http://www.net-snmp.org/wiki/index.php?title=Persistent_Storage_Does_Not_Get_Updated_Immediately&amp;diff=3132&amp;oldid=prev</id>
		<title>Wes at 22:18, 16 October 2007</title>
		<link rel="alternate" type="text/html" href="http://www.net-snmp.org/wiki/index.php?title=Persistent_Storage_Does_Not_Get_Updated_Immediately&amp;diff=3132&amp;oldid=prev"/>
				<updated>2007-10-16T22:18:43Z</updated>
		
		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{GoodAnswer}}&lt;br /&gt;
&lt;br /&gt;
== Question ==&lt;br /&gt;
&lt;br /&gt;
When I make a dynamic modification to the snmp agent it does not immediately update the /var/net-snmp/snmpd.conf file with the new data (example: user password changes, new trap destinations, vacm changes, etc). &lt;br /&gt;
&lt;br /&gt;
If the snmpd crashed, or some one did a &amp;quot;kill -9&amp;quot;, all my changes are lost.&lt;br /&gt;
&lt;br /&gt;
== Answer ==&lt;br /&gt;
&lt;br /&gt;
You&amp;#039;re right!  It doesn&amp;#039;t update it right away.  This is primarily because it was originally conceived as an expensive operation and not worth doing right away.  The agent will save the data upon a proper shutdown, but it won&amp;#039;t if it doesn&amp;#039;t shutdown properly.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; &amp;#039;&amp;#039;You should never kill -9 any daemon except as a last resort!!&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
=== Solution: Force a Save ===&lt;br /&gt;
&lt;br /&gt;
You can, actually, force the snmpd daemon to save the data.  To do this, send a set request to versionSavePersistentData.0 with an integer value of 1.&lt;br /&gt;
&lt;br /&gt;
  snmpset HOST versionSavePersistentData.0 = 1&lt;br /&gt;
&lt;br /&gt;
This will force an immediate save of the data.&lt;br /&gt;
&lt;br /&gt;
[[Category:agent]]&lt;br /&gt;
[[Category:persistence]]&lt;/div&gt;</summary>
		<author><name>Wes</name></author>	</entry>

	</feed>