Comment 15 for bug 328881

Thank you again, Scott! :-)

I had not seen anyone mention that the problem existed prior to Upstart, only that Upstart (more or less) replaced sysvinit, and that before Upstart log.d was working. My apologies if I simply missed it.

I wonder then why putting sysvinit back is suggested as a good workaround. Keep booting and hope that the right telltale message is logged?

May I ask why it is a Wishlist item though when these logs are terribly important?

Erica