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