I was looking into why my syslog messages where all jumbled up when my
computer starts, and I noticed that the 'sleep(1)' in minilog.c designed to
let klogd get its entries in first doesn't seem to to the job anymore.
The rc.syslog messages still get in before the kernel. (Maybe klogd slowed
down?). Just thought I would let you know, as it works quite nicely in
6.2, and now it has a habit of getting a little mixed up. All three souces
of message now get all mixed up - well, its not that bad, but it does
happen. (see bug 23480)
My system is RedHat 7 with many (including sysklogd, initscripts) RawHide
packages and a 2.4.0-ac1 kernel.
Hm, it's really just a timing issue. Not something we can truly
enforce ordering on (and, in any case, the kernel messages
and the syslog messages are intermingled in timing, so unless
we start having the kernel timestamp them and have syslogd
sort them they won't be in order.)
I'll change it to sleep(2), but that may not necessarily help.
Didn't particulary help, but thanks for your efforts.
Another idea: Could rc.sysint dump dmesg into minilog, therefore getting it to
the top of the pile? Anyway, there are much more important things to worry
about than the prettyness (or otherwise) of logfiles.