Robert Story wrote:
On Tue, 08 Mar 2005 17:01:23 -0800 Michael wrote:
MH> I added the code to ignore the SIGPIPE signal and found that I also had
MH> to remove the close(2) to get to the execv() call that runs the trap
MH> handler.
That is really odd. I can't think of why a close call would not
Jude Amal Anand wrote:
Hi all,
First of all thanx to all those ppl who take time off their busy
schedule to HELP US out.
Now i need one favor :-D
i have installed net-snmp (Latest) in my R H linux 9 system.
I configured the agent. Did all the set up necessary and the TRAP is
beautifully received i
Michael Higgins wrote:
Robert Story wrote:
On Fri, 04 Mar 2005 10:46:02 -0800 Michael wrote:
MH> Using a simple setup as described in MH>
http://www.net-snmp.org/tutorial/tutorial-5/commands/snmptrap.html,
when MH> a trap is received, the snmptrapd process fails from a
broken pipe. I
Robert Story wrote:
On Fri, 04 Mar 2005 10:46:02 -0800 Michael wrote:
MH> Using a simple setup as described in
MH> http://www.net-snmp.org/tutorial/tutorial-5/commands/snmptrap.html, when
MH> a trap is received, the snmptrapd process fails from a broken pipe. I
MH> then use the same setup with
[Michael Higgins]:
> I did a little digging and it looks like the problem is in
> agent/mibgroup/utilities/execute.c in run_exec_command(). I don"t know
> a whole lot about how this is architected, but it appears that two
> threads are responsible for making this happen.
Hello List,
I hope this is the right spot to discuss this. My apologies if it isn't
or has been addressed already. I did some searches in the archive and
found other people reporting broken pipe errors but no resolution.
Using a simple setup as described in
http://www.net-snmp.org/tutorial/tu
