bootlogd8
Record boot messages
Usage
/sbin/bootlogd [-c] [-d] [-e] [-r] [-s] [-v] [ -l logfile ] [ -p pidfile ]
Overview
bootlogd runs in the background and copies all strings sent to the /dev/console device to a logfile. If the logfile is not accessible, the messages will be kept in memory until it is.
Options
-
-d -
Do not fork and run in the background.
-
-e -
Print escape characters to the boot log file. This turns off filtering of escape characters and allows tools like GNU less(1) to see and use colour control characters (show the log in colour).
-
-c -
Attempt to write to the logfile even if it does not yet exist. Without this option,
bootlogdwill wait for the logfile to appear before attempting to write to it. This behavior preventsbootlogdfrom creating logfiles under mount points.
-
-r -
If there is an existing logfile called logfile rename it to logfile~ unless logfile~ already exists.
-
-s -
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.
-
-v -
Show version.
-
-l logfile -
Log to this logfile. The default is /var/log/boot.
-
-p pidfile -
Put process-id in this file. The default is no pidfile.
Notes
bootlogd saves log data which includes control characters. The log is technically a text file, but not very easy for humans to read. To address this the readbootlog(1) command can be used to display the boot log without the control characters.
Releases
11 releases since Debian 3.1 (Sarge); the text changed 5 times.
-c since Debian 4.0 (Etch);
-e since Debian 11 (Bullseye);
-s since Debian 4.0 (Etch).