Bug 787575

Summary: No /var/log/dmesg with systemd init
Product: [Fedora] Fedora Reporter: Michael Convey <smconvey>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: iarlyy, jonathan, leigh123linux, lnykryn, notting, plautrba, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-06 09:02:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael Convey 2012-02-06 07:51:37 UTC 
Similar to the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=719398

When using systemd, the kernel boot messages are not dumped into
/var/log/dmesg.  With the old sysv-style init, /etc/rc.d/rc.sysinit included:

# Now that we have all of our basic modules loaded and the kernel going,
# let's dump the syslog ring somewhere so we can find it later
[ -f /var/log/dmesg ] && mv -f /var/log/dmesg /var/log/dmesg.old
dmesg -s 131072 > /var/log/dmesg

This is very useful to have; a single file with the boot messages that is not
logrotated away.
Comment 1 leigh scott 2012-02-06 09:02:15 UTC 

*** This bug has been marked as a duplicate of bug 719398 ***