Bug#678260: lsb-base: lsb fancy boot messages get mixed up

"Didier 'OdyX' Raboud" <[email protected]>
Newsgroups gmane.linux.debian.devel.lsb
Organization Debian - The Universal OS
Message-ID <201206210839.03930.odyx__46427.1574783654$1340261662$gmane$org@debian.org>
tags 678260 +moreinfo
thanks

Hi Thilo, and thanks for your bugreport,

Le mercredi, 20 juin 2012 13.15:46, vous avez écrit :
> the lsb fancy boot messages currently provided via
> '/lib/lsb/init-functions' and
> '/lib/lsb/init-functions.d/20-left-info-blocks' get mixed up.
> Attached is a 1:1 exerpt of boot messages i get with default debian
> lsb which shows the issue.
> 
> Setting the bug severity to 'important' as per reportbugs definition:
> a bug which has a major effect on the usability of a package, without
> rendering it completely unusable to everyone.

That's really weird. In the default configuration (since 2010), initscripts 
uses startpar for the parallel launch of services. From the startpar manpage:

	"The output of each script is buffered and written when the script exit,
	 so output lines of different scripts won't mix. You can modify this
	 behaviour by setting a timeout."

Indeed, /etc/init.d/rc uses a timeout :

	$ grep \(startpar /etc/init.d/rc
	eval "$(startpar -p 4 -t 20 -T 3 -M $1 -P $previous -R $runlevel)"

So maybe the timeouts are too tight for your boot scenario; can you try to 
play with them a bit (in particular increasing -T 3 to -T 15 e.g.) ?

Has this appeared only with 4.1+Debian7 or was it there before ? I suspect 
this might have been introduced by commit 6c5b3ff in 4.1+Debian5 but this 
would imply that your terminal has uncommon capabilities which your log shows 
it doesn't.

So IMHO this is an issue of too tight timeouts in sysv-rc; or do you happen to 
use file-rc ?

Cheers,

OdyX
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.