Bug 3901

Summary: systemd shouldn't replace busybox syslog by default
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Ross Burton <ross.burton>
Component: coreAssignee: Radu Moisan <radu.moisan>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: holger, meta.mr.watcher, meta.watcher, Qi.Chen, radu.moisan, ross.burton, sgw, sstncr
Version: 1.4   
Target Milestone: 1.6 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on:    
Bug Blocks: 5441    

Description Ross Burton 2013-02-18 13:09:36 UTC
The journal is a bit heavy for small systems so it should be disabled by default.

Ideally, we can generate a systemd-journal package so people don't even need to install it.
Comment 1 Ross Burton 2013-02-18 13:25:21 UTC
(Holger's words, for accuracy)

Interestingly the syslog replacing isn't actually working for me (masks syslog.busybox but there's a syslog symlink too).

Either way, this should probably be pulled out into a separate package of some sort, even if it just enables journal and masks out other syslogs.
Comment 2 Radu Moisan 2013-02-25 14:53:50 UTC
(In reply to comment #0)
> The journal is a bit heavy for small systems so it should be disabled by
> default.
> 
> Ideally, we can generate a systemd-journal package so people don't even need
> to install it.

So, do we want to disable journaling (as in build systemd without journal support) or just disable the service by default, but still deploy systemd with journal support compiled in. I'm asking this because I took a peak to see if systemd can be configured/build without journal support and so far could not find a practical way of doing that.
Comment 3 Ross Burton 2013-02-25 15:43:31 UTC
So yes, you can't turn off the journal, or split it out.  From what I understand, it also always opens the syslog socket even if it's not writing anything to do, so if this is the case busybox-syslog (and other syslog daemons) will need to open the proxy syslog socket in /run instead of the kernel socket, as that will be already opened by systemd.
Comment 4 Chen Qi 2013-12-17 07:19:51 UTC
This bug has been solved by Radu in the following commit.

commit 58a6a7c056ff86d69b25528f8235b3bbc8cd8c12
Author: Radu Moisan <radu.moisan@intel.com>
Date:   Thu Jan 17 15:09:58 2013 +0200

    busybox: enable systemd integration for syslogd
    
    (From OE-Core rev: cf3618f9a57e46fb78d5be35d473e2dd5290e961)


So mark this bug as resolved/fixed.

//Chen Qi
Comment 5 Stefan Stanacar 2014-03-10 11:58:00 UTC
Okay, verfied - syslog-busybox is there and running in a systemd image (although IMHO I don't see the point if we still have to have journald)