bootlogd(8) [linux man page]

BOOTLOGD(8)						Linux System Administrator's Manual					       BOOTLOGD(8)

NAME

       bootlogd - record boot messages

SYNOPSIS

       /sbin/bootlogd [-c] [-d] [-r] [-s] [-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 kept in memory until it is.

OPTIONS

       -d     Do not fork and run in the background.

       -c     Attempt to write to the logfile even if it does not yet exist.  Without this option, bootlogd will wait for the  logfile	to  appear
	      before attempting to write to it.  This behavior prevents bootlogd from 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.

BUGS

       Bootlogd works by redirecting the console output from the console device.  (Consequently bootlogd requires PTY support in the  kernel  con-
       figuration.)   It  copies that output to the real console device and to a log file.  There is no standard way of ascertaining the real con-
       sole device if you have a new-style /dev/console device (major 5, minor 1) so bootlogd parses the kernel  command  line	looking  for  con-
       sole=... lines and deduces the real console device from that.  If that syntax is ever changed by the kernel, or a console type is used that
       bootlogd does not know about then bootlogd will not work.

AUTHOR

       Miquel van Smoorenburg, miquels@cistron.nl

SEE ALSO

       dmesg(8),fdatasync(3).

								   Jul 21, 2003 						       BOOTLOGD(8)

BLOGD(8)						       The SuSE boot concept							  BLOGD(8)

NAME

       blogd - boot logging on /dev/console

SYNOPSIS

       /sbin/blogd [/dev/realtty]

DESCRIPTION

       Without	argument blogd determines the real underlying character device of /dev/console.  blogd spawns a pty/tty pair to reconnect the cur-
       rent /dev/console with the slave of the pty/tty pair. During writing information from this slave to the real character device a ring buffer
       is used to hold the information for writing it to an existing logging file.

       To  fetch  the  real  tty  of /dev/console the program showconsole(8) can be used. This has the advantage that blogd will not hold the real
       character device of /dev/console as its controlling tty (would hangup any running getty on that character device).

SIGNALS

       blogd knows a few signal to contol its behavior.

       SIGQUIT, SIGINT, and SIGTERM
	      will cause blogd tries to write out the ring buffer and to exit.

       SIGIO  says blogd that now it is able to write on /var/log/boot.msg which means that the file system is mounted read/write and  the  kernel
	      messages are written to that file.

       SIGSYS says blogd that it should stop writing to disk but continue to repeat messages to the old devices of the system console.

BUGS

       blogd  needs  a	mounted  /proc	and  /dev/pts  file  system  and tries to set the controlling tty to stdin if the real character device of
       /dev/console is not given.  After reading /proc blogd tries to restore the status of the controlling tty to avoid problems with getty  pro-
       cesses.	This can fail because blogd forks to run in the background as a daemon.

FILES

       /proc/<pid of blogd>/stat
	      the stat file of the blogd process.

       /dev/console
	      the system console.

       /var/log/boot.msg
	      logging file which is created by klogd(8) or dmesg(8).

SEE ALSO

       showconsole(8), syslogd(8), klogd(8), dmesg(8), proc(5).

COPYRIGHT

       2000 Werner Fink, 2000 SuSE GmbH Nuernberg, Germany.

AUTHOR

       Werner Fink <werner@suse.de>

3rd Berkeley Distribution					   Nov 10, 2000 							  BLOGD(8)