I submitted patch ID 3293842 to adress this issue. I also raised bug ID: 3293856.
To: "net-snmp-coders@..." <net-snmp-coders@...>
Sent: Wednesday, April 13, 2011 3:23:56 PM
Subject: -register limits to 127 chars the option parameters
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?