| 1 |
covici@××××××××××.com wrote: |
| 2 |
> Dale <rdalek1967@×××××.com> wrote: |
| 3 |
> |
| 4 |
>> Neil Bothwick wrote: |
| 5 |
>>> On Thu, 5 Mar 2015 03:08:46 -0500, German wrote: |
| 6 |
>>> |
| 7 |
>>>> Thanks Dale, done it. Unfortunately it doesn't log everything. For |
| 8 |
>>>> instance "Warning: /lib64/rc/cache is not writable" wasn't written |
| 9 |
>>>> to /var/log/rc.log |
| 10 |
>>> Of course it wasn't. Warnings about /var not being writeable are not going |
| 11 |
>>> to be written to /var. |
| 12 |
>>> |
| 13 |
>>> |
| 14 |
>> Yea, it won't catch everything. This is sort of designed for that point |
| 15 |
>> where one log stops and the other hasn't started yet. This is usually |
| 16 |
>> where dmesg stops and syslog and friends hasn't yet started. Of course, |
| 17 |
>> if /var isn't mounted, well, it has no where to go. |
| 18 |
>> |
| 19 |
>> Isn't those init thingys supposed to fix this sort of thing tho? Isn't |
| 20 |
>> it supposed to store it in memory until /var is mounted and then dump it? |
| 21 |
> Make sure your kernel log buffer is as high as it will go, I use 21 if |
| 22 |
> memory serves which is about a meg or so. Also, I find with an init |
| 23 |
> thingy and using systemd (Yes I know, don't start a flame war), then I |
| 24 |
> see everything in its system journal -- much more even than rc.log used |
| 25 |
> to give me. |
| 26 |
> |
| 27 |
|
| 28 |
I just recall reading somewhere, systemd or not, that that is how it is |
| 29 |
supposed to work. After all, it can't run fsck and such while mounted |
| 30 |
rw from my understanding. It's been to long ago since I read that |
| 31 |
tho. Add in that I'm kick boxing with the flu right now and things are |
| 32 |
fuzzy at least. That kernel log buffer does ring a bell somewhere out |
| 33 |
there. |
| 34 |
|
| 35 |
Dale |
| 36 |
|
| 37 |
:-) :-) |
Archives