| 1 |
On Sunday 28 December 2014 13:32:00 Stroller wrote: |
| 2 |
> On Sat, 27 December 2014, at 1:45 pm, Peter Humphrey |
| 3 |
<peter@××××××××××××.uk> wrote: |
| 4 |
> > On Saturday 27 December 2014 13:10:17 Helmut Jarausch wrote: |
| 5 |
> >> I think this was a long standig bug. Version 3.6.2 seems to have fixed |
| 6 |
> >> this. |
| 7 |
> > |
| 8 |
> > Ah. Well I'm still on 3.4.8. |
| 9 |
> > |
| 10 |
> > Mick, if you don't hear anything from me soonish, it will be safe to |
| 11 |
> > remove the binary stuff using the method I mentioned. |
| 12 |
> |
| 13 |
> If this is bug 406623 then you can remove the spurious binary characters |
| 14 |
> with vim. |
| 15 |
> |
| 16 |
> There are also instructions there on changing your syslogng.conf so |
| 17 |
> they're not produced. |
| 18 |
> |
| 19 |
> However, I'm not sure that this *is* bug 406623, as there seem to be more |
| 20 |
> lines of cr@p produced in Mick's log than I recollect. |
| 21 |
|
| 22 |
It isn't that bug in my case. I don't (didn't) have any non-printing |
| 23 |
characters at the beginning of the file. I didn't check every character of |
| 24 |
course, but I'd guess that a previous file did have non-printables and |
| 25 |
logrotate re-created a file of the same type. |
| 26 |
|
| 27 |
-- |
| 28 |
Rgds |
| 29 |
Peter. |
Archives