Bug 6128 - [patch] Fix S01logging pidfile handling
Summary: [patch] Fix S01logging pidfile handling
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: PC Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-20 13:59 UTC by Tilman Keskinöz
Modified: 2013-05-26 11:36 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Fix syslog initscript (1019 bytes, patch)
2013-03-20 14:00 UTC, Tilman Keskinöz 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tilman Keskinöz 2013-03-20 13:59:18 UTC 
There are two issues with S01logging

1. The initscript relies on the daemon creating a Pidfile, but the relevant option has been disabled in the busybox-1.20.x-config. 
2. The name contains a typo syslogd vs. syslog.

This is fixed with the attached patch.
Comment 1 Tilman Keskinöz 2013-03-20 14:00:49 UTC 
Created attachment 4820 [details]
Fix syslog initscript
Comment 2 Thomas Petazzoni 2013-03-20 14:30:20 UTC 
Thanks. Can you send this as two proper separate patches on the Buildroot mailing list?
Comment 3 Tilman Keskinöz 2013-03-20 15:42:06 UTC 
done, mail waits now for moderator approval
Comment 4 Samuel Martin 2013-05-26 11:36:07 UTC 
The S01logging script typo has been merged.

The pidfile management remains deferred to start-stop-daemon, so the change in the busybox configs is not needed; though any user can enable it.