| 1 |
Stroller <stroller@××××××××××××××××××.uk> writes: |
| 2 |
|
| 3 |
> On Wed, 18 February 2015, at 8:40 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 |
> It's only been closed in the last few weeks. |
| 15 |
|
| 16 |
Still I wonder why it took so long to fix it. |
| 17 |
|
| 18 |
> See for example, comment 36, November last year (i.e. 3 or 4 months old), "This isn't resolved unless commit f4ae768 is backported or >=3.5.6 is stabilised." |
| 19 |
> |
| 20 |
> https://bugs.gentoo.org/show_bug.cgi?id=406623#c36 |
| 21 |
> |
| 22 |
> Since you haven't told us what version of syslog-ng you're running, I think it's reasonable to suspect you've not updated it recently. |
| 23 |
|
| 24 |
The server was installed the week before the last, starting with the |
| 25 |
latest live DVD. It has been updated. I can't tell what version it is |
| 26 |
because it's at work. |
| 27 |
|
| 28 |
> Of course the characters could be left in your logfile from months ago, if you've not been rotating logs. |
| 29 |
> |
| 30 |
> If it's not that bug, though, you should prolly file a new one. |
| 31 |
|
| 32 |
Dunno, I've edited the file and removed the null characters. Time will |
| 33 |
tell whether new ones will be logged or not. |
| 34 |
|
| 35 |
|
| 36 |
IIUC, syslog-ng handles rotating the logs. Do I need to do something to |
| 37 |
make it rotate them? |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
Again we must be afraid of speaking of daemons for fear that daemons |
| 42 |
might swallow us. Finally, this fear has become reasonable. |
Archives