Bug 2926

Summary: sysklogd: syslog.conf should not have tabs within the selector field
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Mihai Lindner <mihai.lindner>
Component: configurationAssignee: Mihai Lindner <mihai.lindner>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: laurentiu.serban, sgw
Version: 1.3   
Target Milestone: 1.3 M4   
Hardware: All   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---
Attachments:
Description Flags
syslog.conf on master:2dec760b79bb7e2e79c33c5127fa64685bd86a18 none

Description Mihai Lindner 2012-08-09 14:46:07 UTC
Created attachment 684 [details]
syslog.conf on master:2dec760b79bb7e2e79c33c5127fa64685bd86a18

Currently the syslog.conf file contains tabs / spaces, within the selector field. (current syslog.conf attached). On LSB images (afaik), where sysklogd is used, syslog is not creating /var/log/messages and, on restart, syslog reports errors of unknown facilities or priorities (e.g. noone, noice, new).

Tabs or spaces should be used in syslog.conf only when separating selectors from actions. From sysklogd's syslog.conf.5 man page:
"""
Every rule consists of two fields, a _selector_ field and an _action_ field. These two fields are separated by one or more spaces or tabs. The selector field specifies a pattern of facilities and priorities belonging to the specified action.
[...]
The selector field consists of two parts, a _facility_ and a _priority_, separated by a period (``.'').
"""
Comment 1 Laurentiu Serban 2012-08-12 22:11:41 UTC
Setting version to 1.3
Comment 2 Mihai Lindner 2012-08-13 13:09:08 UTC
Patch sent to oe-core.
Comment 4 Mihai Lindner 2012-08-29 10:44:06 UTC
.