| 1 |
Stroller <stroller@××××××××××××××××××.uk> writes: |
| 2 |
|
| 3 |
> On Tue, 17 February 2015, at 6:26 pm, lee <lee@××××××××.de> wrote: |
| 4 |
>> |
| 5 |
>> The log file seem to be some sort of binary that doesn't display too |
| 6 |
>> well in less, and there doesn't seem to be any way to read them. |
| 7 |
> |
| 8 |
> I believe this may be bug 406623. |
| 9 |
> |
| 10 |
> https://bugs.gentoo.org/show_bug.cgi?id=406623 |
| 11 |
|
| 12 |
That's almost three years old and should apparently be fixed? |
| 13 |
|
| 14 |
> You can establish whether you're affected by 406623 simply by deleting |
| 15 |
> the character(s) (renaming the log file would probably work, too) and |
| 16 |
> rebooting the system. My experience was that the text logfile is |
| 17 |
> "turned to binary" on reboot - the binary characters were logged as |
| 18 |
> part of the kernel's startup messages. This was repeatable and |
| 19 |
> predictable. |
| 20 |
|
| 21 |
Maybe I'll try it tomorrow --- it's on a server at work which I plan to |
| 22 |
reboot anyway. |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
Again we must be afraid of speaking of daemons for fear that daemons |
| 27 |
might swallow us. Finally, this fear has become reasonable. |
Archives