Re: How to use lsb init-functions

Thomas - My apologies for not getting back to you sooner on this; I've been bouncing around the country due to holidays and job interviews. On 11/22/05, Thomas Hood <[EMAIL PROTECTED]> wrote: > In trying to convert the initscripts in the "initscripts" package to use > the logging functions in /lib

Re: How to use lsb init-functions

Benjamin Mesing wrote: Only a thought that occured to me when reading this: Did you think about how your approach will work once the proposed parallel boot script execution is implemented? If you want to see how it could look like when you have scripts with parallel output you could have a loo

Re: How to use lsb init-functions

On Tue, 22 Nov 2005, Benjamin Mesing wrote: > Only a thought that occured to me when reading this: Did you think about > how your approach will work once the proposed parallel boot script > execution is implemented? It will be replaced by whatever is in the parallel system. So don't worry too much

Re: How to use lsb init-functions

Only a thought that occured to me when reading this: Did you think about how your approach will work once the proposed parallel boot script execution is implemented? Best regards Ben -- Please do not sent any email to the [EMAIL PROTECTED] - all email not originating from the mailing list will be

Re: How to use lsb init-functions

[Gabor Gombas] > I'm thinking that it would be very useful to redirect stderr to a > file (say /var/log/boot/.error). It happens far too often > that the error message scrolls off the screen, then > fonty/gdm/etc. starts making scrolling back impossible. There are ideas to send boot messages to s

Re: How to use lsb init-functions

On Tue, Nov 22, 2005 at 12:21:37PM +0100, Thomas Hood wrote: > But the problem is that foo may produce output and this will break up the nice > single-line format. I don't mind deverting stdout to /dev/null, but I am > reluctant to divert stderr to /dev/null and error messages will also break up

How to use lsb init-functions

In trying to convert the initscripts in the "initscripts" package to use the logging functions in /lib/lsb/init-functions I have run into some problems. Currently there are two sets of functions intended to implement the several kinds of messages normally output by Debian and Ubuntu initscripts.