Ok, I see. Well, then this behavior is probably preferred. Thankyou
2008/1/27, Sergei Ivanov <[EMAIL PROTECTED]>: > > > Yes, I sure understand that you don't want to be a maintainer for it, > that > > would probably be quite a lot of work. For me the [ok] comes on it's own > > separate: > > Sun Jan 27 21:52:32 2008: * Starting system message bus dbus > > Sun Jan 27 21:52:32 2008: [ OK ] > > > > Is this intentional? Otherwise this seems much nicer than before. > > Well, bootlogd *has* a maintainer, it's Debian sysvinit team. Maybe I'll > send the fixes > there some day. > > The OK placement is yes, sort of intentional. They use a lot of terminal > trickery to make > output look better, and logging it correctly would require many changes to > the code. > I had to choose from a couple of simple rules, and the other choices led > to worse results. > After all, this "OK" is a separate message and its timing may be useful. > > You can make it appear on the same line by changing the source as follows. > Go to bootlog.c line 361, there will be a part of switch like this: > > case '\n': > case '\r": > ... > > Change it to: > > case '\r': > break; > case '\n': > ... > > (that is, interchange the two cases and insert "break;" between them). > But then you will lose, among other things, the summary of a long fsck run > (it will be truncated as a part of one extra long line). > > -- > logd not running > https://bugs.launchpad.net/bugs/98955 > You received this bug notification because you are a direct subscriber > of the bug. > -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
