First off let me apologize to Dave, that last email was my fault I don't
know what I did wrong and it didn't get posted to the list. Secondly I
would like to thank everyone who helped me track this problem down.

thanks to you all!

-Steph



|---------+---------------------------->
|         |           Dave Shield      |
|         |           <[EMAIL PROTECTED]|
|         |           iv.ac.uk>        |
|         |                            |
|         |           10/28/2004 08:54 |
|         |           AM               |
|         |                            |
|---------+---------------------------->
  
>------------------------------------------------------------------------------------------------------------------------|
  |                                                                                    
                                    |
  |       To:       Stephanos Kotsakis/NY/WGM/[EMAIL PROTECTED]                        
                                               |
  |       cc:       [EMAIL PROTECTED]                                                  
                 |
  |       Subject:  Re: snmptrapd traphandle problem please help                       
                                    |
  
>------------------------------------------------------------------------------------------------------------------------|




        [ First - *please* don't mail me privately, without copying
              any responses to the mailing list.  I don't have the time
         or inclination to offer private, unpaid, SNMP consultancy.
              Keep discussions to the list, where others can both learn
              and offer advice.  Thanks.   ]


> Here are my results. the simplest way to make the problem stop is to
simply
> add one read statement in the traphandler script:
>
> #!/bin/bash
>
> read
>
> is enough to solve the problem of the snmptrapd exiting out when there it
> receives a trap specified in snmptrapd.conf.

Yes - that's pretty much what I expected.
This is a clear bug that we need to fix.
(But not until *after* 5.2!)

> I implemented this bash script
> and had excelent results
>
> #!/bin/bash
>
> read one
> read two
> read three
> echo -e "$one $two $three" >> /root/testfile
>
> here is the contents of /root/testfile
>
> 172.24.3.50 172.24.3.50 .1.3.6.1.2.1.1.3.0 12:1:58:03.66
> 172.24.3.50 172.24.3.50 .1.3.6.1.2.1.1.3.0 12:1:58:05.96
> 172.24.3.50 172.24.3.50 .1.3.6.1.2.1.1.3.0 12:1:58:13.66
> 172.24.3.50 172.24.3.50 .1.3.6.1.2.1.1.3.0 12:1:58:15.96
> 172.24.3.50 172.24.3.50 .1.3.6.1.2.1.1.3.0 12:1:58:23.67
> 172.24.3.50 172.24.3.50 .1.3.6.1.2.1.1.3.0 12:1:58:25.96
> 172.24.3.50 172.24.3.50 .1.3.6.1.2.1.1.3.0 12:1:58:33.67
> 172.24.3.50 172.24.3.50 .1.3.6.1.2.1.1.3.0 12:1:58:35.95
> 172.24.3.50 172.24.3.50 .1.3.6.1.2.1.1.3.0 12:1:58:43.67
> 172.24.3.50 172.24.3.50 .1.3.6.1.2.1.1.3.0 12:1:58:45.96
> 172.24.3.50 172.24.3.50 .1.3.6.1.2.1.1.3.0 12:1:58:53.66

Looks good.
(Well, it looks pretty boring and not very meaningful to be
 honest,  but you know what I mean!)


> My only question now is it seems that I still can't get the traphandler
to
> output to stdout, I must have the output go to file, any ideas on this?

Ummmm.....
  Well, as a general rule, there's nothing to guarantee that there will
*be* a "standard output" channel for things to be displayed to.  The
trap daemon is designed to be run as just that - a daemon.  So it will
typically be run in the background, not connected to a terminal at all.

  I'm not sure how meaningful it is for a trap handler script to
print to stdout, or what the trap daemon should do with output
from such a script.
  We'd probably need a discussion about the most appropriate behaviour
before starting to implement anything.

Dave
>





< END >


-----------------------------------------
The information contained in this email message is intended only for use of
the individual or entity named above. If the reader of this message is not
the intended recipient, or the employee or agent responsible to deliver it
to the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If
you have received this communication in error, please immediately notify us
by email ([EMAIL PROTECTED]), and destroy the original message. Thank you



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Net-snmp-users mailing list
[EMAIL PROTECTED]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to