Question on using syslog-ng
I am looking for a package that will provide application level logging and it looks to me like syslog-ng has the capabilities I am looking for. I am not quite sure that I would want to replace syslogd with syslog-ng. Would it be possible to have syslog-ng coexist with syslogd by having it listen on a different port? I would have write a version of syslog to communicate using the alternate port. Correct? Thanks, Ken ---------------------------------------------- Kenneth J. Heeres Johns Hopkins University Group Supervisor Applied Physics Laboratory Ground Applications Group (SIG) Johns Hopkins Road Laurel, MD 20723-6099 Wash.: 240-228-5853 Balt: 443-778-5853 kenneth.heeres@jhuapl.edu
I am not quite sure that I would want to replace syslogd with syslog-ng. Would it be possible to have syslog-ng coexist with syslogd by having it listen on a different port? I would have write a version of syslog to communicate using the alternate port. Correct?
yes. have syslog-ng listen on /var/run/myapp/log and send your messages to that socket instead of /dev/log -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
I just installed syslog-ng as a syslog concentrator for multiple network management applications that feed off syslog. I need to do the same thing with SNMP traps. I tried simple source and destination on the SNMP udp ports and it does grab and forward but not in any manner that makes sense to SNMP listeners on the detinations. Has anyone done any work on SNMP specific sources or destinations? If not, is anyone else interested and can anyone give me a gentle push into the sources (like where the udp source/destination code is)? mwa
I don't know if anyone has answered this, and I'm too lazy to look in the archive. But here it goes: On Tue, Jun 05, 2001 at 01:44:30PM -0400, Mark W. Alexander wrote:
I just installed syslog-ng as a syslog concentrator for multiple network management applications that feed off syslog. I need to do the same thing with SNMP traps. I tried simple source and destination on the SNMP udp ports and it does grab and forward but not in any manner that makes sense to SNMP listeners on the detinations.
Assuming you were using syslog-ng this make sense. Syslog and SNMP Trap are very different protocols.
Has anyone done any work on SNMP specific sources or destinations? If not, is anyone else interested and can anyone give me a gentle push into the sources (like where the udp source/destination code is)?
I have, but since I am not a big fan of SNMP I used an SNMP Trap daemon that turned everything into syslog traffic (decoding what it could of those nasty SNMP OIDs). This has worked well for me, as it unifies logging into one resource. http://net-snmp.sourceforge.net/ Another package, Scotty, is also quite good, and is written in TCL/Tk. I don't have the URL handy. ---------------------------------------------------------------------------- __o Bradley Arlt Email: arlt@cpsc.ucalgary.ca o__ _ \<_ WWW: www.acs.ucalgary.ca/~bdarlt _>/ _ (_)/(_) -Eat well, sleep peacefully, drink lots, and ride like hell. (_)\(_)
participants (4)
-
Balazs Scheidler
-
Brad Arlt
-
Heeres, Ken
-
Mark W. Alexander