If you run:
/etc/init.d/bootlogd </dev/console >/dev/console 2>&1
it works OK. Running bootlogd after the system has booted will
capture future output to the console, which may be useful, and the
expected behavior of scripts in /etc/init.d is that their services can
be stopped and started at will from a command prompt, so it's quite
surprising that bootlogd's init script doesn't work that way.
Googling for the error message in the subject of this bug report will
provide some evidence that this is a common cause of confusion.
The fix is very simple, when running bootlogd from the init script,
redirect standard input, standard output, and standard error to the
console:
start-stop-daemon --start --quiet --exec $DAEMON -- \
$BOOTLOGD_OPTS \
</dev/console >/dev/console 2>/dev/console
-----Scott.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
