OK, after a couple of weeks of investigation I think I've got to the
bottom of the issue.
Thanks by the way for the suggestions received from Thomas Anders and Dave
Shields. To Thomas, 5.3 suffers the same issue and to Dave, yes, passing
an Install Prefix avoids the issue, but as some of our customers require
to use v5.0.9 to maintain compatibility with the v4.xx level of IBM
Director, I wanted to get a fix that would work with any level of
net-snmp. The Install Prefix capability arrived between versions 5.0.9 and
5.2.1.
Anyway, the culprit was found to be the %makeinstall macro in
/usr/lib/rpm/suse_macros. The format of the macro of "%makeinstall make
-DESTDIR=%{buildroot} install" did not have the desired effect of
installing in the temporary root. I therefore commented out that line and
let the build follow the generic %makeinstall in /usr/lib/macros with
success. For those who are interested, RedHat has the same macro in both
/usr/lib/rpm/macros and /usr/lib/rpm/redhat/macros in a form which matches
that in the /usr/lib./rpm/macros file in SLES9.
A couple of other modifications I had to make were to modify the directory
in which the snmpd start script is installed. The /etc/rc.d/init,d tree
does not match the structure native to Suse. RedHat links /etc/init.d to
/etc/init.d but Suse has a link of /etc/rc.d to /etc/init.d - this meant
that the script ended up in /etc/init.d/init.d. In addition, Suse does not
have the "daemon" function, I had to substitute "startproc". Finally the
networking test does not work in Suse, I had to comment out the references
to /etc/sysconfig/network and the ${NETWORK} variable and ensure that
networking was loaded via the load order in rc3.d. I'm open to suggestions
as to how to test for the network being "up" in SLES9.
A couple of handy hints for anyone compiling the older, 5.0.9, level with
Suse. First you need to enter the Version and Release levels in the spec
file.The spec file can also be improved by removing the %dir in the line
"%dir %{_datadir}/snmp/", this avoids a list of "Installed but Unpackaged"
files. It also renders the similar line for the /smnp/snmpconf-data
superfluous, I note that it is commented out in the 5.2.1 spec file, where
the %dir is also notable by its absence. Lastly, the installation section
for the snmpd script can be lifted from the 5.2.1 spec file, with
appropriate modifications to the target directory as noted above, thus
saving a manual step of extracting the script from the dist subdirectory
where it resides as snmpd-init.d.
Regards,
David Blair
+44 (0)1475 555518
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
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
