summaryrefslogtreecommitdiff
path: root/keymaps-force-release/samsung-90x3a
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2012-09-17 17:42:13 +0200
committerLennart Poettering <lennart@poettering.net>2012-09-17 17:47:47 +0200
commita866073d35dea05e6f3e56328d3eb6436943e7e6 (patch)
tree8d8fbadda92216a862b9411d82d5bfb866939ed0 /keymaps-force-release/samsung-90x3a
parent72edcff5db936e54cfc322d9392ec46e2428fd9b (diff)
main: when transitioning from initrd to the main system log to kmsg
When the new PID is invoked the journal socket from the initrd might still be around. Due to the default log target being journal we'd log to that initially when the new main systemd initializes even if the kernel command line included a directive to redirect systemd's logging elsewhere. With this fix we initially always log to kmsg now, if we are PID1, and only after parsing the kernel cmdline try to open the journal if that's desired. (The effective benefit of this is that SELinux performance data is now logged again to kmsg like it used to be.)
Diffstat (limited to 'keymaps-force-release/samsung-90x3a')
0 files changed, 0 insertions, 0 deletions