Hi,
I discovered there is a limit of 127 characters for the option parameters when
registering snmpd as a Windows service via the <snmpd -register> command.
For example, specifying the following command:
snmpd -register -c "C:\ProgramData\Cassidian\RCS 9500\Config\CM
DB\Active\cassidian.pmc.cmdb.snmpd.conf,C:\ProgramData\Cassidian\RCS
9500\Config\snmpd.conf"
does not work as the argument is 135 characters long and will be truncated to
“C:\ProgramData\Cassidian\RCS 9500\Config\CM
DB\Active\cassidian.pmc.cmdb.snmpd.conf,C:\ProgramData\Cassidian\RCS
9500\Config\sn”
The snmpd.log file shows:
c : No such file or directory
c: No such file or directory
Warning: no access control information configured.
(Config search path: c:/usr/etc/snmp;c:/usr/share/snmp;c:/usr/lib)
It's unlikely this agent can serve any useful purpose in this state.
Run "snmpconf -g basic_setup" to help you configure the snmpd.conf file for
this agent.
NET-SNMP version 5.5.1
To validate my theory, I renamed the snmpd.conf file to “sn”; therefore
limiting the argument to 127 characters and snmpd starts working just fine
again!
Same result with the 5.6.1 and 5.5 versions.
Note that the argument stored in the registry is not limited to 127 characters,
therefore the problem seems to be when snmpd is reading the argument from the
registry.
It this a known limitation? Is there a fix for this?
Regards,
Sylvain
------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now! http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
