Added reference to readbootlog to the bootlogd manual page. This
should allow Debian bug #725123 to be closed.
Jesse Smith
5 years ago
| 51 | 51 |
produced by bootlogd. The output is displayed cleaned up so there
|
| 52 | 52 |
are no control characters. This avoids the need to use sed or related
|
| 53 | 53 |
tools to try to clean up the contents of the log.
|
| 54 | |
* Added manual page for readbootlog program.
|
|
54 |
* Added manual page for readbootlog program. Updated bootlogd page
|
|
55 |
to reference it. Closes Debian bug #725123.
|
| 55 | 56 |
|
| 56 | 57 |
|
| 57 | 58 |
sysvinit (2.91) world; urgency=low
|
| 54 | 54 |
Log to this logfile. The default is \fI/var/log/boot\fP.
|
| 55 | 55 |
.IP "\fB\-p\fP \fIpidfile\fP"
|
| 56 | 56 |
Put process-id in this file. The default is no pidfile.
|
|
57 |
.SH NOTES
|
|
58 |
bootlogd saves log data which includes control characters. The log is
|
|
59 |
technically a text file, but not very easy for humans to read. To address
|
|
60 |
this the readbootlog(1) command can be used to display the boot log
|
|
61 |
without the control characters.
|
| 57 | 62 |
.SH BUGS
|
| 58 | 63 |
Bootlogd works by redirecting the console output from the console device.
|
| 59 | 64 |
(Consequently \fBbootlogd\fP requires PTY support in the kernel configuration.)
|
|
| 68 | 73 |
.SH AUTHOR
|
| 69 | 74 |
Miquel van Smoorenburg, miquels@cistron.nl
|
| 70 | 75 |
.SH "SEE ALSO"
|
| 71 | |
.BR dmesg (8), fdatasync (3).
|
|
76 |
.BR dmesg (8), fdatasync (3), readbootlog(1).
|