Bug 292651 - Sys::Syslog: Trailing #012#000
Sys::Syslog: Trailing #012#000
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: perl (Show other bugs)
rawhide
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Marcela Mašláňová
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-09-16 18:23 EDT by Jan Kratochvil
Modified: 2008-02-27 07:22 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-27 07:22:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
The incomplete fix. (799 bytes, patch)
2007-09-16 18:23 EDT, Jan Kratochvil
no flags Details | Diff

  None (edit)
Description Jan Kratochvil 2007-09-16 18:23:13 EDT
Description of problem:
All the perl-generated syslog messages now have trailing excessive #012#000

Version-Release number of selected component (if applicable):
perl-5.8.8-25.fc8.x86_64
rsyslog-1.19.2-1.fc8.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. perl -MSys::Syslog -e 'syslog "info","abc";'

Actual results:
Sep 17 00:17:59 host0 lace: abc#012#000

Expected results:
Sep 17 00:17:44 host0 lace: abc

Additional info:
There is a similiar tracked bug:
  http://rt.cpan.org/Public/Bug/Display.html?id=24431
The attached fix is not completely correct:
The trailing "\0" is expected iff AF_UNIX+SOCK_STREAM connection is used.
  (But there are IMO other bugs preventing to use AF_UNIX+SOCK_STREAM even
   if one would like to force Sys::Syslog to use it.)
The trailing "\n" is expected iff stderr is used.
Comment 1 Jan Kratochvil 2007-09-16 18:23:13 EDT
Created attachment 196811 [details]
The incomplete fix.
Comment 2 Marcela Mašláňová 2008-02-27 07:22:21 EST
I didn't reproduce it. I'd similar problem with cron some time ago, so that was
problem of rsyslog.

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