www.LinuxHowtos.org howtos, tips&tricks and tutorials for linux

from small one page howto to huge articles all in one place

Other .linuxhowtos.org sites: toolsntoys.linuxhowtos.org
gentoo.linuxhowtos.org
forums.linuxhowtos.org

poll results

Last additions:

Disable Anti-Aliasing fonts

words:

186

views:

7419

userrating:

no votes yet

May 25th. 2007:

Words

491

Views

8563

why adblockers are bad

handy one-liners for sed (Unix stream editor)

Tutorial:

handy one-liners for sed (Unix stream editor)

words:

4078

views:

23270

userrating:

no votes yet

rotating apache logfiles with cronolog

words:

294

views:

8877

userrating:

no votes yet

You are here: manpages

BOOTLOGD

Section: Linux System Administrator's Manual (8)
Updated: Jul 21, 2003
Index Return to Main Contents

NAME

bootlogd - record boot messages

SYNOPSIS

/sbin/bootlogd [-d] [-r] [-v] [ -l logfile ] [ -p pidfile ]

DESCRIPTION

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 buffered in-memory until it is.

OPTIONS

-d: Do not fork and run in the background.
-r: If there is an existing logfile called logfile rename it to logfile~ unless logfile~ already exists.
-v: Show version.
-l: Log to this logfile. The default is /var/log/boot.
-p: Put process-id in this file. The default is no pidfile.

BUGS

Bootlogd works by redirecting the console output from the console device. It copies that output to the real console device and a logfile. There is no standard way to find out the real console device if you have a new-style /dev/console device (major 5, minor 1). Bootlogd tries to parse the kernel command line, looking for console= lines and deducts the real console device from that. If that syntax is ever changed by the kernel, or a console-type is used bootlogd does not know about, bootlogd will not work.