[email protected] wrote: > Dale <[email protected]> wrote: > >> Neil Bothwick wrote: >>> On Thu, 5 Mar 2015 03:08:46 -0500, German wrote: >>> >>>> Thanks Dale, done it. Unfortunately it doesn't log everything. For >>>> instance "Warning: /lib64/rc/cache is not writable" wasn't written >>>> to /var/log/rc.log >>> Of course it wasn't. Warnings about /var not being writeable are not going >>> to be written to /var. >>> >>> >> Yea, it won't catch everything. This is sort of designed for that point >> where one log stops and the other hasn't started yet. This is usually >> where dmesg stops and syslog and friends hasn't yet started. Of course, >> if /var isn't mounted, well, it has no where to go. >> >> Isn't those init thingys supposed to fix this sort of thing tho? Isn't >> it supposed to store it in memory until /var is mounted and then dump it? > Make sure your kernel log buffer is as high as it will go, I use 21 if > memory serves which is about a meg or so. Also, I find with an init > thingy and using systemd (Yes I know, don't start a flame war), then I > see everything in its system journal -- much more even than rc.log used > to give me. >
I just recall reading somewhere, systemd or not, that that is how it is supposed to work. After all, it can't run fsck and such while mounted rw from my understanding. It's been to long ago since I read that tho. Add in that I'm kick boxing with the flu right now and things are fuzzy at least. That kernel log buffer does ring a bell somewhere out there. Dale :-) :-)
