reopen 323749
thanks

This problem came back when switching to LSB functions.  log_begin_msg doesn't
output a trailing newline, so on GNU/kFreeBSD the message output is cluttered,
like this:

  Rebooting...BlahBlah Blah
  BlahBlah Blah

Instead of:

  Rebooting...
  BlahBlah Blah
  BlahBlah Blah

I'm not sure how to fix this.  LSB functions (as described in lsb-base's
README.Debian) don't seem to consider the situation when output from
another app follows the beginning message (much like dhclient when invoked
by ifupdown, but in this case output can't be redirected to /dev/null because
it comes from the kernel).

Any ideas?

-- 
Robert Millan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to