]>
Commit | Line | Data |
---|---|---|
a74aeac6 PR |
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" "" "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 [ \-r ] | |
26 | .RB [ \-s ] | |
27 | .RB [ \-v ] | |
28 | .RB [ " -l logfile " ] | |
29 | .RB [ " -p pidfile " ] | |
30 | .SH DESCRIPTION | |
31 | \fBBootlogd\fP runs in the background and copies all strings sent to the | |
32 | \fI/dev/console\fP device to a logfile. If the logfile is not accessible, | |
33 | the messages will be kept in memory until it is. | |
34 | .SH OPTIONS | |
35 | .IP \fB\-d\fP | |
36 | Do not fork and run in the background. | |
37 | .IP \fB\-c\fP | |
38 | Attempt to write to the logfile even if it does not yet exist. | |
39 | Without this option, | |
40 | .B bootlogd | |
41 | will wait for the logfile to appear before attempting to write to it. | |
42 | This behavior prevents bootlogd from creating logfiles under mount points. | |
43 | .IP \fB\-r\fP | |
44 | If there is an existing logfile called \fIlogfile\fP rename it to | |
45 | \fIlogfile~\fP unless \fIlogfile~\fP already exists. | |
46 | .IP \fB\-s\fP | |
47 | Ensure that the data is written to the file after each line by calling | |
48 | .BR fdatasync (3). | |
49 | This will slow down a | |
50 | .BR fsck (8) | |
51 | process running in parallel. | |
52 | .IP \fB\-v\fP | |
53 | Show version. | |
54 | .IP "\fB\-l\fP \fIlogfile\fP" | |
55 | Log to this logfile. The default is \fI/var/log/boot\fP. | |
56 | .IP "\fB\-p\fP \fIpidfile\fP" | |
57 | Put process-id in this file. The default is no pidfile. | |
58 | .SH BUGS | |
59 | Bootlogd works by redirecting the console output from the console device. | |
60 | (Consequently \fBbootlogd\fP requires PTY support in the kernel configuration.) | |
61 | It copies that output to the real console device and to a log file. | |
62 | There is no standard way of ascertaining the real console device | |
63 | if you have a new-style \fI/dev/console\fP device (major 5, minor 1) | |
64 | so \fBbootlogd\fP parses the kernel command line looking for | |
65 | \fBconsole=...\fP lines and deduces the real console device from that. | |
66 | If that syntax is ever changed by the kernel, or a console type is used that | |
67 | \fBbootlogd\fP does not know about then \fBbootlogd\fP will not work. | |
68 | ||
69 | .SH AUTHOR | |
70 | Miquel van Smoorenburg, miquels@cistron.nl | |
71 | .SH "SEE ALSO" | |
72 | .BR dmesg (8), fdatasync (3). |