#12286 NORM 13.1.0: [systemd-]journald should not forward to syslog

Zarro Boogs per Child bugtracker at laptop.org
Thu Nov 8 09:24:02 EST 2012

#12286: [systemd-]journald should not forward to syslog
           Reporter:  shawnl     |       Owner:  dsd          
               Type:  defect     |      Status:  assigned     
           Priority:  normal     |   Milestone:  13.1.0       
          Component:  distro     |     Version:  not specified
         Resolution:             |    Keywords:  systemd      
        Next_action:  never set  |    Verified:  0            
Deployment_affected:             |   Blockedby:               
           Blocking:             |  
Changes (by dsd):

  * owner:  pbrobinson => dsd
  * status:  new => assigned
  * milestone:  Not Triaged => 13.1.0


 Thanks Shawn.

 This will cause some messages that were previously in /var/log/messages to
 be no longer available, though? That will be a bit confusing for our
 developers who have to break existing habits.

 Instead, is it possible for us to do the opposite: disable journald's
 internal logging, keep things going to syslog? (just for this release)

 In the next development cycle we should definitely do this "right" -
 remove syslog from our builds altogether and just have journald. (We can't
 do this immediately because we're in stabilisation stages.)

 These changes would be done in our build system (stop installing rsyslog,
 configure journald to our needs) and communicated via the devel mailing
 list. The only configuration tweak we do to rsyslog is that we limit it to
 using 2mb of space - that would need to be mirrored in journald
 configuration if possible. If you'd be interested in looking into how that
 would happen, the build system is described at

Ticket URL: <http://dev.laptop.org/ticket/12286#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system

More information about the Bugs mailing list