> On Mon, 10 Jan 2005 15:02:29 +, Dave Shield <[EMAIL PROTECTED]> said:
Dave> I'd say the current documentation is fairly vague about how to
Dave> use it. That's partly why I'm writing the book :-)
Hey! I only write vague documentation, you should know that. At
least there *is* documen
> On Mon, 10 Jan 2005 19:30:25 + (GMT), Mayuresh Dhagamwar <[EMAIL
> PROTECTED]> said:
Mayuresh> Now can I specify the version of snmp (1,2 or 3) at runtime
Mayuresh> so that same snmpd file can act as v1, or v2 agent without
Mayuresh> recompilation? If yes then how and where do I spe
The bug is fixed in 5.2 version. I noticed the bug in 5.1.2 version as
well. Thanks for the info.
Jaiber John.
On Sat, 8 Jan 2005 16:59:38 +0100, Magnus Fromreide
<[EMAIL PROTECTED]> wrote:
> On Sat, Jan 08, 2005 at 08:48:37PM +0530, jaiber john wrote:
> > hello,
> >
> > I've noticed a problem wh
Hi
Folks:
I hope this it the
right place to post this.
Building snmpd for
win32, I've found the following bug.
In tools.c's
netsnmp_getenv() version 5.2.1:
If the "temp = getenv(name);" on line 939 returns non NULL, the next
interesting statement executed is:
if (temp)
{
set
Hi,
I want to ask a simple query. I have downloaded net-snmp-5.1.1 source code and compiled it to form a snmpd executable for mips linux.
Now can I specify the version of snmp (1,2 or 3) at runtime so that same snmpd file can act as v1, or v2 agent without recompilation? If yes then how and whe
Hi,
I'm running snmpd (4.2.6) on debian and uses the pass_persist functionality.
My agent acts well and respond properly...but,... ;-).
My concern is that it appears to me as if there is one pass process started for
each remote ip quering the agent..?
When i query my agent from my first comput
On Fri, 2005-01-07 at 16:29, Robert Story wrote:
> On Fri, 07 Jan 2005 10:34:45 + Dave wrote:
> DS> It appears that in most cases, the MfD framework effectively splits
> DS> each pass of the "traditional" SET handling model
>
> Yes. The idea is that eventually the agent will use the baby step
On Fri, 2005-01-07 at 15:23, Robert Story wrote:
> DS> (I was a bit surprised to see that you'd applied this
> DS> to the 5-2-patches line as well, since I thought that was
> DS> currently in pre-release freeze, but that's by-the-by).
>
> I thought comment changes were always fair game. And comm
On Fri, 2005-01-07 at 16:29, Robert Story wrote:
> DS> The obvious oddity is the Commit handling - there's nothing
> DS> that works on committing individual columns.
>
> Correct. This is only because the tables I've dealt with all keep column data
> in the same place, so I haven't needed commits f
On Mon, 2005-01-10 at 05:25, Wes Hardaker wrote:
> Dave> Firstly, adding this stash-caching to an existing MIB
> Dave> relies on injecting the stash-cache handler *after* having
> Dave> registered the handler chain with the main agent (so that
> Dave> the stash-cache kicks in before the normal proc
On Fri, 2005-01-07 at 15:23, Robert Story wrote:
> DS> I'm appending a new "mfd-access" file, that could be used
> DS> to generate code which omits all of the cache-related
> DS> processing altogether...
> What I probably would have done would have been to define a new variable to
> make the cache
Hello,
If I send a vendor specific v2 trap using snmptrap utility then can I receive this trap on windows machine? If yes where will I see the received trap (notification) ?
Thanks and regards,
-Mayuresh.
ALL-NEW
Yahoo! Messenger
- all new features - even more fun!
Greg Wickham wrote:
In addition to these problems there definitely appears to be memory
leakage in the perl. Running memory thousands of consecutive large
requests it is quite obvious that the perl process is consuming an
increasing amount of memory). The equivalent problem in 'C' shows no
sign of
13 matches
Mail list logo
