Bug 249037 - rsyslog shows newlines at the ends of messages
rsyslog shows newlines at the ends of messages
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: rsyslog (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Peter Vrabec
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-07-20 10:22 EDT by Jonathan Kamens
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-07-30 06:17:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jonathan Kamens 2007-07-20 10:22:45 EDT
Some of my syslog messages just started showing "#012" at the end of them.  I
suspect this is because the programs calling the messages are sticking newlines
at the end of them.  sysklogd stripped these off but rsyslog apparently doesn't.
 I think it should, both for compatibility with sysklogd and because it makes sense.
Comment 1 Rainer Gerhards 2007-07-23 05:27:42 EDT
That's probably a config line issue. I can not directly mangle the files on
reception, because that would break compatibility with current IETF
standardization efforts. However, the templates should take care of this problem
- maybe I missed something there. Could you post your (r)syslog.conf?
Comment 2 Rainer Gerhards 2007-07-23 06:16:34 EDT
I've tackled this beast in a different way. There is a new config directive

$DropTrailingLFOnReception on|off

The default is on. If we run into trouble with IETF movements, it can always be
turned off (this is most probably a problem with syslog-sign only). The current
handling (even on) is in sync with what -syslog-protocol specifies. Will be part
of 1.17.2.
Comment 3 Peter Vrabec 2007-07-23 11:13:38 EDT
upstream version 1.17.2 was just built, could you test it please.

Note You need to log in before you can comment on or make changes to this bug.