Hello,
Thanks for your answers.
I solved the install problem. The problem was that some "scripts" using
the "sh shell" and others the "bash shell". I changed the symbolic link
/bin/sh -> /bin/dash to /bin/sh -> /bin/bash. Then the intallation was
successfull.
I run the "snmpd" daemon that it is on "/usr/local/sbin/snmpd" and it
show this message:
error while loading shared libraries: libnetsnmpagent.so.15: cannot open
shared object file: No such file or directory
My other problem is the "agentx" not start and my application doesn't work
>> - the "agentx" wasn't into "/var" directory
>This will be created automatically when you run the agent.
>It's not created as part of "make install"
How I solve my problems?
Thanks
2011/11/10 Dave Shield <[email protected]>
> On 10 November 2011 10:03, francisco moreno <[email protected]> wrote:
>
> > - I downloaded "net-snmp-5.4.4.tar.gz" package from sourceforge.
> > - I unziped this (tar xzvf net-snmp-5.4.4.tar.gz) into "/etc" directory
> > - I have installed "libperl-dev" library
> > - Next, I followed the steps of installation (I saw INSTALL file)
> > * ./configure
> > * make
> > * sudo make install
> >
> > When all process has finished, I could observe:
> > - the "snmpd" daemon wasn't into "/etc/init.d" directory
>
> No - the snmpd daemon will probably be installed as /usr/local/sbin/snmpd
> The 'init.d' directory is used for start-up scripts for the various
> system daemons.
>
> There's an example for such a script in 'dist/snmp-init.d'
> but you'd need to copy it into place yourself.
> And I'm not sure whether this is modelled on the Ubuntu-style
> version of such startup scripts, or a Fedora template. So you might
> need to tweak it to match your setup.
>
> But the agent itself will bin in a binary directory, not /etc/init.d
>
>
> > - the "agentx" wasn't into "/var" directory
>
> This will be created automatically when you run the agent.
> It's not created as part of "make install"
>
>
> > - the configuration files don't exist. The "snmpd.conf" file was not
> into
> > "/etc/snmp" directory and the "snmpd" file was not into "/etc/default"
> > directory
>
> We don't install a default snmpd.conf, because we don't know how
> you want to run the agent. You should create this yourself, to match
> your own requirements.
> The simplest such file would probably contain simply
>
> rocommunity public
>
> (or you could replace "public" with a different community name)
>
> Note that for a self-compiled version of the agent, this should probably
> be installed as /usr/local/etc/snmpd.conf rather than
> /etc/snmp/snmpd.conf
>
> I wouldn't expect anything to be installed under /etc/defaults.
> I can't think why that would be relevant to SNMP.
>
>
> Dave
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
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
