Debian Codegraph @

upstream/debian-unstable/man8/bootlogd.8

raw
1 '\" -*- coding: UTF-8 -*-
2 .\" Copyright (C) 1998-2003 Miquel van Smoorenburg.
3 .\"
4 .\" This program is free software; you can redistribute it and/or modify
5 .\" it under the terms of the GNU General Public License as published by
6 .\" the Free Software Foundation; either version 2 of the License, or
7 .\" (at your option) any later version.
8 .\"
9 .\" This program is distributed in the hope that it will be useful,
10 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
11 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 .\" GNU General Public License for more details.
13 .\"
14 .\" You should have received a copy of the GNU General Public License
15 .\" along with this program; if not, write to the Free Software
16 .\" Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
17 .\"
18 .TH BOOTLOGD 8 "Jul 21, 2003" "sysvinit " "Linux System Administrator's Manual"
19 .SH NAME
20 bootlogd \- record boot messages
21 .SH SYNOPSIS
22 .B /sbin/bootlogd
23 .RB [ \-c ]
24 .RB [ \-d ]
25 .RB [ \-e ]
26 .RB [ \-r ]
27 .RB [ \-s ]
28 .RB [ \-v ]
29 .RI [ " \fB-l\fP logfile " ]
30 .RI [ " \fB-p\fP pidfile " ]
31 .SH DESCRIPTION
32 \fBbootlogd\fP runs in the background and copies all strings sent to the
33 \fI/dev/console\fP device to a logfile. If the \fIlogfile\fP is not accessible,
34 the messages will be kept in memory until it is.
35 .SH OPTIONS
36 .IP \fB\-d\fP
37 Do not fork and run in the background.
38 .IP \fB\-e\fP
39 Print escape characters to the boot log file. This turns off filtering of
40 escape characters and allows tools like GNU \fBless\fP(1) to see and use
41 colour control characters (show the log in colour).
42 .IP \fB\-c\fP
43 Attempt to write to the logfile even if it does not yet exist.
44 Without this option, \fBbootlogd\fP will wait for the logfile to appear before
45 attempting to write to it. This behavior prevents \fBbootlogd\fP from creating
46 logfiles under mount points.
47 .IP \fB\-r\fP
48 If there is an existing logfile called \fIlogfile\fP rename it to
49 \fIlogfile~\fP unless \fIlogfile~\fP already exists.
50 .IP \fB\-s\fP
51 Ensure that the data is written to the file after each line by calling
52 .BR fdatasync (3).
53 This will slow down a
54 .BR fsck (8)
55 process running in parallel.
56 .IP \fB\-v\fP
57 Show version.
58 .IP "\fB\-l\fP \fIlogfile\fP"
59 Log to this logfile. The default is \fI/var/log/boot\fP.
60 .IP "\fB\-p\fP \fIpidfile\fP"
61 Put process-id in this file. The default is no pidfile.
62 .SH NOTES
63 \fBbootlogd\fP saves log data which includes control characters. The log is
64 technically a text file, but not very easy for humans to read. To address
65 this the \fBreadbootlog\fP(1) command can be used to display the boot log
66 without the control characters.
67 .SH BUGS
68 \fBbootlogd\fP works by redirecting the console output from the console device.
69 (Consequently \fBbootlogd\fP requires PTY support in the kernel configuration.)
70 It copies that output to the real console device and to a log file.
71 There is no standard way of ascertaining the real console device
72 if you have a new-style \fI/dev/console\fP device (major 5, minor 1)
73 so \fBbootlogd\fP parses the kernel command line looking for
74 \fBconsole=...\fP lines and deduces the real console device from that.
75 If that syntax is ever changed by the kernel, or a console type is used that
76 \fBbootlogd\fP does not know about then \fBbootlogd\fP will not work.
77
78 .SH AUTHOR
79 .MT miquels@\:cistron\:.nl
80 Miquel van Smoorenburg
81 .ME
82 .SH "SEE ALSO"
83 .BR dmesg (8),
84 .BR fdatasync (3),
85 .BR readbootlog (1)