I'm using openrc-0.2.5 (but the error also occured for earlier versions) in combination with rc_parallal="YES" in /etc/rc.conf. During boot, the output (boot console output as well as /var/log/rc.log) sometimes gets scrambled like this (regard the line after syslog-ng): dbus | * Starting D-BUS system messagebus ... netmount | * Mounting network filesystems ... hddtemp | * Starting hddtemp daemon ... [ ok ] syslog-ng | * Starting syslog-ng ... 4m[G [32 34m[km o 4m] [1m] avahi-daemon | * Starting avahi-daemon ... [ ok ] hald | * Starting Hardware Abstraction Layer daemon ... anacron | * Running anacron ... ntp-client | * Setting clock via the NTP client 'ntpdate' ... [ ok ] [ ok ] The init scripts mixing their output is of course expected behaviour when parallely booting, but each line should still be intact, right? I've been observing this for a few weeks now and it's fairly unpredictable when the scrambling occurs, or if it occurs at all, which is of course a typical symptom for a bug in parallelisation. I'm running a dual core, so there should actually be non-pseudo parallelism. Reproducible: Sometimes Steps to Reproduce: 1. configure rc_parallel="YES" on a multicore system 2. boot Actual Results: Boot output (sometimes) gets scrambled on the console as well as in /var/log/rc.log Expected Results: Linewise, not totally scrambled output :) * sys-apps/openrc [R 0.2.5] Reasons: sys-apps/baselayout-2.0.0:0::installed -debug ncurses pam unicode kernel: (-FreeBSD) (linux) on ~amd64 intel dual core: CHOST="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2 -pipe" CXXFLAGS="${CFLAGS}" I'll leave the severity on 'normal', as I don't know if the output is the only thing that gets messed up.
(In reply to comment #0) > The init scripts mixing their output is of course expected behaviour when > parallely booting, but each line should still be intact, right? There is no guarantee that is the case as the syntax is like so ebegin "some message" some_command eend $? "some_command failed" Those are 3 seperate commands and all are fighting for console. The tricky one is eend as it's logic is "go up one line and then to the rightmost column. Then step back for the text, finally print the text". If we have a display daemon instead of dumping to console via a spinlock we may be able to fix this. But don't expect that anytime soon - unless someone else wants to code it :)
Fixed in 0.3.0
