blogger(8) [suse man page]

BLOGGER(8)						       The SuSE boot concept							BLOGGER(8)

NAME

       Blogger - writes messages to a running blogd process

SYNOPSIS

       blogger [-n|-d|-f|-s|-u] "a message here"

DESCRIPTION

       blogger	is  used  to  send  messages  to  the  blogd  process during boot phase.  These messages will only appear in the boot logging file
       /var/log/boot.msg and not on /dev/console.

OPTIONS

       -n     Declare the following message as a <notice>.  This is the default.

       -d     Use thist to add the leading string <done> to the message.

       -f     Use thist to add the leading string <failed> to the message.

       -s     Use thist to add the leading string <skipped> to the message.

       -u     Use thist to add the leading string <unused> to the message.

FILES

       /dev/blog
	      the named pipe (FIFO) used as message channel to the blogd process.

SEE ALSO

       blogd(8), console(4), tty(4), proc(5).

COPYRIGHT

       2001 Werner Fink, 2001 SuSE GmbH Nuernberg, Germany.

AUTHOR

       Werner Fink <werner@suse.de>

3rd Berkeley Distribution					   Jan 26, 2001 							BLOGGER(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)