Hi Greeting:
It seems the result of "net-snmp-config --configure-options" is not right. It
only echo the first option. There are more configure options in the echo list but only
the first one was displayed.
And the "net-snmp-cofig --agent-libs" and "net-snmp-config --external-agent-li
Update.
Thomas Anders sent me an email pointing me in the right direction.
The problem is in the /usr/bin/net-snmp-config script is wrong.
All the case statements are wrong for an OSX box on a PPC platform. I
modified mine to the following, then tried the snmpdemoapp.c with the
Makefile and
Hi Robert -
Yeah - I got the issue resolved. The /usr/bin/net-snmp-config file is
misconfigured at the initial install (for OSX systems) for every case
entry -- cflags and all the others. I modified the case entry for each
-- setting cflags appropriately and the compile worked perfect with the
> ... I was unclear. Here's what I'm doing:
>
> - writing a createUser directive to /var/net-snmp/snmpd.conf
>
> - Poking the reconfig bit in the agent's MIB
> ...
Here's the rub. I wan't actually poking the reconfig bit as I thought I was. That
works now. Never mind.
---
> On Wed, 15 Sep 2004 13:09:54 -0400 [EMAIL PROTECTED] wrote:
> CRC> I'm trying to use read_config_read_octet_string() (in 5.1.1)
> and I'm not
> CRC> getting the results I expect.
> ...
> No, the function is inconsistent in its use of the len parameter.
> In the case
> of a non-hex string and a
> On Wed, 15 Sep 2004 13:09:54 -0400 [EMAIL PROTECTED] wrote:
> CRC> I'm trying to use read_config_read_octet_string() (in 5.1.1)
> and I'm not
> CRC> getting the results I expect.
>
> Use the source, Luke...
Yeah, I'm trying (that's where I found the snippet I posted). But it's not exactly a
> On Thu, 16 Sep 2004 08:33:06 -0400 [EMAIL PROTECTED] wrote:
> CRC> (Ooops. The first time I replied only to Thomas.)
> CRC>
> CRC> > Yes, that's current behaviour. The persistent file is only
> saved on
> CRC> > shutdown.However, I'd tend to agree that it'd be useful to
> be able
> CRC> > to
I have an administrative user, admin, who uses a configuration utility to manipulate
parts of the system setup, including snmp users. To do this, I've set
/var/net-snmp/snmpd.conf to look like:
# ls -ld /var/net-snmp/
drwxrwxr-x2 root admin 0 Jan 1 02:14 /var/net-snmp/
On Thu, 16 Sep 2004 08:33:06 -0400 [EMAIL PROTECTED] wrote:
CRC> (Ooops. The first time I replied only to Thomas.)
CRC>
CRC> > Yes, that's current behaviour. The persistent file is only saved on
CRC> > shutdown.However, I'd tend to agree that it'd be useful to be able
CRC> > to force the *running
On Wed, 15 Sep 2004 13:09:54 -0400 [EMAIL PROTECTED] wrote:
CRC> I'm trying to use read_config_read_octet_string() (in 5.1.1) and I'm not
CRC> getting the results I expect.
Use the source, Luke...
CRC> But, if I do:
CRC>...
CRC>char* pt;
CRC>size_t len;
CRC>char value[32];
CRC>
On Tue, 14 Sep 2004 16:05:25 -0700 (PDT) unoimdman wrote:
U> I moved the original snmp.conf file, restarted
U> snmpd but the process is killed shortly after.
Any log messages?
Try running in the foreground (snmpd -f -L).
Try running it under gdb, and see if it crashes or exits.
--
Robert Story
On Wed, 15 Sep 2004 14:30:41 +0200 Dalton wrote:
DH> When I issue "make snmpdemoapp"
DH> I get the following:
DH>
DH> make snmpdemoapp
DH> gcc -I. `net-snmp-config --cflags` -c -o snmpdemoapp.o snmpdemoapp.c
DH> gcc: cannot read specs file for arch `i386'
What do you get if you run 'net-snmp-co
On Wed, 15 Sep 2004 07:44:47 +0200 Thomaschewski, wrote:
TH> Thanks for your help. Now I understood the different between
TH> both but what happens, when both options are standing in the
TH> snmpd.conf?
TH>
TH> Is "com2sec" able to forbidd access when "rocommunity" allows it?
Maybe, but not in a
[Moved to users, to get a wider audience]
On Wed, 15 Sep 2004 20:05:32 -0400 Michael wrote:
MJS> Tha FAQ and README.OSX files need to be updated.
MJS>
MJS> Which versions do either of you run on ?
I've built it and done very minimal testing ('oh look, it starts') on 10.3.5.
MJS> What is the rec
Hi all,
I am a newbie on this group.
I am working with the NET-SNMP library version 5.1.1 and I need some help
about BER encoding rules for a relative object identifier.
In particular I am referring to the ITU-T Recommendation X.690 - Amendment
1 (06/99).
It seems to me that the BER encoding for r
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Baumgart
Alexander
Sent: Donnerstag, 16. September 2004 13:24
To: Net-Snmp Users (E-mail)
Subject: ARM Cross compile
Hello,
i cant cross compile net-snmp on a i686 for arm anymore. ;(
yesterd
(Ooops. The first time I replied only to Thomas.)
> [EMAIL PROTECTED] wrote:
> > The man page for snmpd.conf says:
> >
> >...
> >This directive should be placed into the /var/net-
> >snmp/snmpd.conf file instead of the other normal
> >locations. The reason is that the inform
Hello,
i cant cross compile net-snmp on a i686 for arm anymore. ;(
yesterday all work great today i get a error:
C compiler cannot create executables
i used ./configure --target=arm-linux --with-cc=arm-linux-gcc
--with-cflags=-mbig-endian --with-endianness=big --
[EMAIL PROTECTED] wrote:
The man page for snmpd.conf says:
...
This directive should be placed into the /var/net-
snmp/snmpd.conf file instead of the other normal
locations. The reason is that the information is
read from the file and then the line is removed
(eliminati
19 matches
Mail list logo
