[prev in list] [next in list] [prev in thread] [next in thread] 

List:       net-snmp-bugs
Subject:    [ net-snmp-Bugs-1437822 ] trap syslogging fragile/confusing, 5.3.0.1
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2006-02-24 1:48:31
Message-ID: E1FCS4N-0003wj-HO () sc8-sf-web2 ! sourceforge ! net
[Download RAW message or body]

Bugs item #1437822, was opened at 2006-02-24 01:48
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1437822&group_id=12694

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: snmptrapd
Group: solaris
Status: Open
Resolution: None
Priority: 5
Submitted By: Kris (tinker105)
Assigned to: Nobody/Anonymous (nobody)
Summary: trap syslogging fragile/confusing, 5.3.0.1

Initial Comment:
I'm running on Solaris 8 and 10, but I don't think 
platform is relevant.
I've already submitted one bug report about -D turning 
off the default syslogging of traps.  However, now 
that I've trudged through the code some more, I have 
more to report.

1. The ONLY way for traps to get to the syslog appears 
to be "by default" (i.e. there is no explicit way to 
send them there).  This wouldn't be so bad if there 
weren't several things that will prevent the default 
logging from being setup:
- -D (as described previously)
- -L (at least I wasn't able to find a combination of 
settings that would do the trick)
- AgentX (i.e. if snmptrapd is able to connect to a 
master agent, it logs some messages, which turns on 
stderr logging by default:
No log handling enabled - turning on stderr logging
NET-SNMP version 5.3.0.1 AgentX subagent connected
registering pdu failed: 263!
...

2. There _appear_ to be 2 places in snmptrapd.c where 
the default syslogging is turned on (near lines 950 
and 1090).  From testing, it appears that only the 
stuff around line 950 (setting up syslog_handler) logs 
traps.

Issue #1 is clearly something that needs to be fixed.  
Perhaps the code could be moved earlier (e.g. before 
the subagent_init() call)?  I still don't understand 
though whether -L should be able to send traps to the 
syslog.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1437822&group_id=12694


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Net-snmp-bugs mailing list
Net-snmp-bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-bugs
[prev in list] [next in list] [prev in thread] [next in thread]