| 1 |
On Wed, 18 February 2015, at 8:40 pm, lee <lee@××××××××.de> wrote: |
| 2 |
>>> |
| 3 |
>>> The log file seem to be some sort of binary that doesn't display too |
| 4 |
>>> well in less, and there doesn't seem to be any way to read them. |
| 5 |
>> |
| 6 |
>> I believe this may be bug 406623. |
| 7 |
>> |
| 8 |
>> https://bugs.gentoo.org/show_bug.cgi?id=406623 |
| 9 |
> |
| 10 |
> That's almost three years old and should apparently be fixed? |
| 11 |
|
| 12 |
It's only been closed in the last few weeks. |
| 13 |
|
| 14 |
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." |
| 15 |
|
| 16 |
https://bugs.gentoo.org/show_bug.cgi?id=406623#c36 |
| 17 |
|
| 18 |
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. |
| 19 |
|
| 20 |
Of course the characters could be left in your logfile from months ago, if you've not been rotating logs. |
| 21 |
|
| 22 |
If it's not that bug, though, you should prolly file a new one. |
| 23 |
|
| 24 |
Stroller. |
Archives