> Remember that this object is writeable via SNMP
> so can be given a new value using a SET command.
> It's also possible to configure an initial value
> using the "sysname" directive in snmpd.conf.
>
> If either of these have happened, then it probably
> wouldn't be appropriate to track changes to the
> underlying hostname.
agreed. i am aware of the sysname directive in
snmpd.conf too. in that case, snmpd shall first see if
snmp specific sysname has already set in the conf
file. if user ever set sysname via snmpset (where you
can detect it from the existance of psysname), then
snmpd shall never update its sysname from the system
itself.
what i concern is actually: in the case of the
psysname in the snmpd.conf is not found (means user
never SET hostname via snmpset), the snmp agent can
reflect the hostname correctly and up-to-date.
Thanks!
Regards,
SK
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
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
