Both patches, the one in the bug and the mine, seemed to work fine. Maybe I missed the patch at the bottom of the bug report at that time and came up with mine. I had forgotten about it since my patch worked for me.
Thanks for the response. Joel On Fri, 2004-10-01 at 10:01, Robert Story wrote: > On Tue, 27 Apr 2004 11:31:41 -0400 Joel wrote: > JP> On Thu, 2004-04-15 at 12:33, Joel Parker wrote: > JP> > I've been trying to use disman monitoring support on linux machines > JP> > running net-snmp 5.1.1. [...] If a process being monitored isn't > JP> > running on my host I do get traps. The problem I have is that other > JP> > processes being monitored have traps sent when they are still running. > JP> > > JP> > I found the same exact problem described in the bug tracker from 2002: > JP> > http://sourceforge.net/tracker/index.php? > JP> > func=detail&aid=615744&group_id=12694&atid=112694 > JP> > > JP> I was able to stop these events from being sent to my trap server. I > JP> was only seeing this problem on machines running glibc 2.2. In any > JP> event I landed up modifing mteTriggerTable.c with the following patch > JP> and it didn't seem to break anything on multiple machines with varying > JP> versions of glibc. I was only interested in traps being sent from the > JP> proc, disk and load average tables. > > Hi Joel, > > Sorry for the delay in getting back to you. Did you try the one line patch > listing in that problem report? If not, can you try it and see if it works as > well as the patch you came up with?
signature.asc
Description: This is a digitally signed message part
