From: <no...@so...> - 2001-10-23 18:05:48
|
Patches item #474176, was opened at 2001-10-23 11:05 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=312694&aid=474176&group_id=12694 Category: None Group: None Status: Open Resolution: None Priority: 7 Submitted By: John Naylon (jbpn) Assigned to: John Naylon (jbpn) Summary: Persisten system group Initial Comment: This patch is a diff against the current head of the tree but it ought to apply to v4-2-patches with only trivial changes (if any). Synopsis: sysName.0, sysLocation.0, sysContact.0 made persistent to /var/ucd-snmp/snmpd.conf using "psysname", "psyslocation", "psyscontact" tokens. These are NOT intended to be used in regular configuration files and as such are not advertised. If config parsing finds BOTH a syslocation token (in e.g. /usr/local/share/snmp/snmpd.conf) and a psyslocation token, the value from the syslocation token has precedence, and a warning is emitted. If a syslocation token is found, this is in a file that snmpd is not able to modify. Therefore changes to sysLocation.0 cannot be made persistent, and therefore the logic is that they should not be allowed at all. wrongValue is returned in this case when a SET is attempted. (?? is this the best value -- what about notWritable ??) Otherwise, setting sysLocation.0 causes a psyslocation token to be written to /var/ucd-snmp/snmpd.conf (immediately and also at shutdown). ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=312694&aid=474176&group_id=12694 |