bootlogd - record boot messages
] [ -l logfile
] [ -p pidfile
runs in the background and copies all strings sent to the
device to a logfile. If the logfile is not accessible, the
messages will be kept in memory until it is.
- Do not fork and run in the background.
- Attempt to write to the logfile even if it does not yet
exist. Without this option, bootlogd will wait for the logfile to
appear before attempting to write to it. This behavior prevents bootlogd
from creating logfiles under mount points.
- If there is an existing logfile called logfile
rename it to logfile~ unless logfile~ already exists.
- Ensure that the data is written to the file after each line
by calling fdatasync(3). This will slow down a fsck(8)
process running in parallel.
- Show version.
- -l logfile
- Log to this logfile. The default is
- -p pidfile
- Put process-id in this file. The default is no
Bootlogd works by redirecting the console output from the console device.
requires PTY support in the kernel
configuration.) It copies that output to the real console device and to a log
file. There is no standard way of ascertaining the real console device if you
have a new-style /dev/console
device (major 5, minor 1) so
parses the kernel command line looking for console=...
lines and deduces the real console device from that. If that syntax is ever
changed by the kernel, or a console type is used that bootlogd
know about then bootlogd
will not work.
Miquel van Smoorenburg, email@example.com