Title: RE: IPV6 support for Linux
Robert,
I have tried v5.1.2.rc2, it still can't launch as
snmpd udp:161,tcp:161,udp6:161,tcp6:161
Thanks,
Fong
-Original Message- From:
[EMAIL PROTECTED] on behalf of Fong Tsui
Sent: Wed 8/18/2004 3:51 PM To:
[EMAIL PROTECTED] Cc: Li
Robert,
Is there a patch which can solve this issue: launch IPv6 and IPv4 together?
snmpd udp:161,tcp:161,udp6:161,tcp6:161
At this moment, I can not update to v5.1.2 version. I am using 5.0.9 and hope to solve
this.
Thanks,
Fong
-Original Message-
From: Robert Story (Coders) [ma
Dave Shield wrote:
Thomas> I'd prefer to see this argument go away by updating "COPYING" in
Thomas> *all* 5.x branches to the version in CVS MAIN. :)
It has been.
So once 5.1.2 is released, that would be the most recent public version
and hence what should appear on the web site.
You didn't think t
AV/IT.sm <[EMAIL PROTECTED]> wrote:
>I got this error:
>
>configure: WARNING: netinet6/nd6.h: present but cannot be compiled
>configure: WARNING: netinet6/nd6.h: check for missing prerequisite headers?
>
>
>foomaster# uname -ra
>FreeBSD foomaster.local 4.10-RELEASE-p2 FreeBSD 4.10-RELEASE-p2 #3:
> > I've just applied a patch to the main development code line,
> > that should avoid trying to validate such local connections
> > against the hosts.{allow,deny} files.
>
> Is there going to be another release or a patch (for 5.1.2) soon?
There doesn't seem to have been an outburst of problems
> Oooh sorry about that one. I should have read the guidelines here
> http://www.cs.huji.ac.il/support/docs/autobook/autobook_209.html#SEC209
> more carefully.
>
> I've uploaded a patch to the patch that should fix the problem for you.
That patch has now been applied to the main developm
> I got this error:
>
> configure: WARNING: netinet6/nd6.h: present but cannot be compiled
> configure: WARNING: netinet6/nd6.h: check for missing prerequisite headers?
> foomaster# uname -ra
> FreeBSD foomaster.local 4.10-RELEASE-p2 FreeBSD 4.10-RELEASE-p2 #3:
Yes - this is a known problem on
I have applied the part of patch #702435 (only changes in snmp_agent.c) for memory
leak in SET data in subagent. Also, I applied patch #991561 which may or may not
relevant. It seems working. There is no leak. I don't know whether it will crash or
not yet. I will test more.
Thanks,
Fong
---
> Attached is a patch that solves the problem for me by always using the
> context string the AgentX subagent registered for communicating with it.
> This makes it independent of the mapping between SNMP request context
> and AgentX registration context.
OK - I've applied that to the main developm
> i need to know how we can get the proxy information .
What proxy (and proxy information) are you interested in?
> i need to know what is apache server.?
Apache is a Web server.
> how can we monitor apache servises.
That really depends on what information you're trying to get at.
There ar
10 matches
Mail list logo
