Thanks for the education.
The way I built and prepared for the net-snmp agent is to use the configure options
such as:
./configure --with-default-snmp-version=2 --with-sys-contact="[EMAIL PROTECTED]"
--with-sys-location=Unknown --with-logfile="/var/log/snmpd.log"
--with-persistent-directory="/var/net-snmp" --disable-manuals --disable-scripts
--prefix="/usr/local" --with-install-prefix="/tmp"
Then another person (integrated the whole product) used the following script (I only
listed the part related to the net-snmp installation) to install the agent on the
target machine -
.
..
...
cd ${PRODUCT_SRC}/net-snmp
make >> ${LOG_DIR}/make-MAIN.log
make install >> ${LOG_DIR}/make-MAIN.log
cd /tmp; tar cvf net-snmp-target.tar usr >> ${LOG_DIR}/make-MAIN.log
cp /tmp/net-snmp-target.tar ${UPDATE_DIR}
rm -Rf /tmp/usr
rm -f /tmp/net-snmp-target.tar
...
..
.
I could run the snmpwalk on my development machine (Linux 2.4.21-mtd.1, single CPU).
But the target machine (Linux 2.4.21-mtd.1, dual CPU)
would be crashed if a snmpwalk to the ifTable. This happened on 5.1.1. It doesn't
happen on 5.0.6.
DS> these are re-linked with the installed versions of the libraries, and it's *those*
binaries which should
DS> be installed, not the wrapper scripts
If the tools in /usr/local/bin are not the actual binaries. How did the agent know to
response and return objects to the snmpwalk? I think I still haven't fully
comprehended how the net-snmp
tools work yet.
Thanks,
Jim
-----Original Message-----
From: Dave Shield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 27, 2004 5:08 PM
To: Jim Su
Cc: Net-Snmp-Users
Subject: Re: Size increased 10 times bigger in an older version of net-snmp
> The "file snmpbulkwalk" (created in 5.0.6) is -
> snmpbulkwalk: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
> for GNU/Linux 2.0.0, dynamically linked (uses shared libs), not stripped
> The "file snmpbulkwalk" (created in 5.1.1) is -
> snmpbulkwalk: Bourne shell script text executable
Yup - that's what I half expected.
The 5.1.1 "binaries" aren't actually the real binaries at all.
You've installed the "libtool" wrappers, which are only meant to
be there temporarily while you're working within the build tree
(using the local versions of the various libraries)
The real binaries are squirreled away in a hidden directory.
When you type "make install", these are re-linked with the installed
versions of the libraries, and it's *those* binaries which should
be installed, not the wrapper scripts.
Did you install the suite manually, by any chance? Just copying
the "binaries" from the apps directory? 'Cos that Will Not Work.
Dave
N5,mz{([Ɯ*'zXnW{jeƭZVǭv-+%yb Zh)ඊ%"{-jYR'urj梷ׯj[hudjf&Ĉ
?{4}4M4k"ثy_z'z&j)b b^ b,y+^jǬyay%"
Zh{.n+Zb{!lb,y+b?+-wwyǫ
