reassign 507722 sysvinit
thanks

On 23/02/2009 Jonas Meurer wrote:
> In bugreport #507722, Jochen Schulz pointed out, that insserv and
> CONCURRENCY=shell in combination with bootlogd enabled leads to lots of
> boot messages to being suppressed. One of the suppressed messages is the
> cryptsetup passphrase prompt (from the cryptdisks initscript).
> 
> This happens only with both CONCURRENCY=shell and BOOTLOGD_ENABLE=Yes
> set. If either of the both is not set, then everything works as
> expected. Thus the issue is neither only a problem with bootlogd, nor
> with insserv, but only with the combination of both.
> 
> I guess that this behaviour is not intended and can be considered as a
> bug.
> 
> Some testing revealed that not only the cryptdisks boot prompt is
> suppressed. Instead, all boot messages from initscripts run after
> bootlogd start and before bootlogd stop aren't displayed. The only
> exception are the kernel messages produced by mount.
> 
> I don't know much about bootlogd and insserv. Could you give me advice
> on how to go on with the bugreport? Shall I reassign it to sysvinit or
> insserv? Or do further debugging?

I'm reassigning the bugreport to sysvinit as this apparently seems to be
a bug in bootlogd.

I even believe that this is the same bug as described in bugreport
#532904

greetings,
 jonas

Attachment: signature.asc
Description: Digital signature

Reply via email to