[Bug 16] New: program destination driver no longer sends TAG to STDIN in 2. 0.6
https://bugzilla.balabit.com/show_bug.cgi?id=16 Summary: program destination driver no longer sends TAG to STDIN in 2.0.6 Product: syslog-ng Version: 2.0.x Platform: PC OS/Version: Linux Status: NEW Severity: major Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: llarian@llarian.net Type of the Report: --- Estimated Hours: 0.0 After an upgrade from 1.6.11 to 2.0.6, it appears that the program destination driver no longer sends the priority/facility tag to stdout, despite the docs saying it transfers using the wire protocol of syslog. The following is the output of a perl script that does nothing but log stdin: Jan 15 15:46:57 192.168.105.10/206.208.46.253 10054: Jan 15 15:46:55.948 PST: %SYS-5-CONFIG_I: Configured from console by dylanv on vty0 (192.168.113.34) 1.6.11 prefixes this with the correct <45> output. Is this expected behavior and is there a way to get it to send the raw syslog packet to the program destination? -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=16 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution| |WONTFIX Status|NEW |RESOLVED --- Comment #1 from Balazs Scheidler <bazsi@balabit.hu> 2008-01-16 08:37:20 --- true enough, this might have changed in 2.0.x, although not intentionally. I'm not sure thought that I want to change this so late in the syslog-ng 2.0.x development state, as other might already have got used to the new behaviour and I don't want to break their production system. You can get back the old behaviour by specifying a template explicitly: destination d_prog { program("/bin/script" template("<$PRI>$DATE $HOST $MSG\n"); }; So, I'm closing this ticket as WONTFIX, please reopen if you disagree. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=16 Dylan Vanderhoof <llarian@llarian.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX | Status|RESOLVED |REOPENED --- Comment #2 from Dylan Vanderhoof <llarian@llarian.net> 2008-01-16 08:56:50 --- (In reply to comment #1)
true enough, this might have changed in 2.0.x, although not intentionally. I'm not sure thought that I want to change this so late in the syslog-ng 2.0.x development state, as other might already have got used to the new behaviour and I don't want to break their production system. You can get back the old behaviour by specifying a template explicitly: destination d_prog { program("/bin/script" template("<$PRI>$DATE $HOST $MSG\n"); }; So, I'm closing this ticket as WONTFIX, please reopen if you disagree.
Then this is a documentation bug. The reference manual included with syslog-ng 2.0 has the following in section 2.6: "The default message format that is sent to the program matches the BSD syslog protocol, e.g. it includes the priority value in addition to the format used in logfiles."
From the perspective of a developer, I'm inclined to agree with the docs in terms of the preferred default format for program output, but your point about development systems is well taken, and there is a workaround.
-- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=16 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |frobert@balabit.hu --- Comment #3 from Balazs Scheidler <bazsi@balabit.hu> 2008-01-16 10:57:39 --- You are right, the documentation needs to be fixed. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=16 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW AssignedTo|bazsi@balabit.hu |frobert@balabit.hu -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=16 Robert Fekete <frobert@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution| |FIXED Status|NEW |RESOLVED --- Comment #4 from Robert Fekete <frobert@balabit.hu> 2008-01-17 14:54:19 --- I have corrected this problem in The syslog-ng Administrator Guide version 1.0.16, which is already available on the website (http://www.balabit.com/support/documentation). Thank you very much for noticing this doc bug. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
bugzilla＠bugzilla.balabit.com