After configuring the master agent the following library files exist in the
"/usr/local/lib" directory:
libnetsnmp.a
libnetsnmp.la
libnetsnmp.so
libnetsnmp.so.15
libnetsnmp.so.15.0.0
libnetsnmpagent.a
libnetsnmpagent.la
libnetsnmpagent.so
libnetsnmpagent.so.15
libnetsnmpagent.so.15.0.0
libnetsnmp
Wes Hardaker wrote:
> I don't believe so. It does do size checking of the data that it is
> writing, so a overflow is not possible. It would produce an error and
> the packet couldn't be sent, but it shouldn't produce a buffer overflow.
> Please let us know (immediately) if you find a specific ca
When I perform the "configure" command I provide a "--prefix=/usr/local" option
value to indicate the NetSNMP package should be installed into "/usr/local"
after it has been cross-compiled and I run "make install". After this occurs,
I can copy the files I need to my target hardware box and pla
Yes, as long as the two boxes are identical or the file are compiled for
the platform they're going to.
See the instructions in README.solaris (they work on non-Solaris as
well) for creating a binary package.
basically:
mkdir /usr/local/dist
make install prefix=/usr/local/dist/usr/local
exec_
Ok, I think I understand now . I should build NetSNMP as the "complete
package" and simply copy over the necessary elements onto our hardware box:
library files
snmpd.conf
snmpd executable
Basically, I can build NetSNMP with the applications, man pages, scripts, mibs,
etc... and then just
Yes, I think you might be right. Using the basic/standard package would be
ideal, however, the total size of everything installed into the "/usr/local"
directory is about 20Megs. Add in my subagent code and the total might be
around 23Megs.This might be too big I will see.
When you d
On 17/07/07, Need Help <[EMAIL PROTECTED]> wrote:
> I am new to SNMP and I am
> not familiar with how people use SNMP in the "real world"
I suggest you talk to your customers, to find out what they expect
from the boxes you sell. We don't know anything about what so
It seems NetSNMP comes integrated with a lot MIB file functionality and a lot
of the MIB.txt text files are located in the "/usr/local/share/snmp/mibs"
directory as well.
My company wants to support the specific "OC-STB-HOST-MIB" MIB file, so I was
wondering whether certain of these integrated
> "AL" == Aleksandr Lomanov <[EMAIL PROTECTED]> writes:
AL> The forward asn encoding is not finished.
It's finished as far as it is going to go feature-wise. The code is
very old and much of it derived from a previous library that came from
the cmu-snmp package.
AL> It doesn't support memor
Hello, all!
Wes Hardaker wrote:
> I'm not sure how I think about removing the forward encoding... I'll
> have to think about it. One ramification is that if we remove the
> generic BER routines, there could be applications that still make use of
> the forwarding encoding ones (why they're using
On 16/07/07, Need Help <[EMAIL PROTECTED]> wrote:
> 1) If I wanted to perform a SNMP request on a particular port (ie: 705),
> then I guess I would execute the command with 127.0.0.1:705 ?
Yes.
Although you wouldn't send SNMP requests to port 705.
> 2) Should I be using port 705, or is port 161
On 16/07/07, Need Help <[EMAIL PROTECTED]> wrote:
> Does the following "netstat" output seem reasonable?
No.
> Here is "netstat -an" output after starting the master agent on port 705
> only:
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address
On 16/07/07, Jayson Robinson <[EMAIL PROTECTED]> wrote:
>
> Are there any
> known disk related memory leaks in 5.3?
I'm not sure.
At the very least, we'd suggest trying with a more recent release,
either 5.3.1 (the latest
13 matches
Mail list logo
