On Sun, Feb 22, 2015 at 6:48 PM, lee <lee@yagibdah.de> wrote:
>
> Stroller <stroller@stellar.eclipse.co.uk> writes:
>
> > On Wed, 18 February 2015, at 8:40 pm, lee <lee@yagibdah.de> wrote:
> >>>>
> >>>> The log file seem to be some sort of binary that doesn't display too
> >>>> well in less, and there doesn't seem to be any way to read them.
> >>>
> >>> I believe this may be bug 406623.
> >>>
> >>> https://bugs.gentoo.org/show_bug.cgi?id=406623
> >>
> >> That's almost three years old and should apparently be fixed?
> >
> > It's only been closed in the last few weeks.
>
> Still I wonder why it took so long to fix it.
>
> > 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."
> >
> > https://bugs.gentoo.org/show_bug.cgi?id=406623#c36
> >
> > 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.
>
> The server was installed the week before the last, starting with the
> latest live DVD.  It has been updated.  I can't tell what version it is
> because it's at work.
>
> > Of course the characters could be left in your logfile from months ago, if you've not been rotating logs.
> >
> > If it's not that bug, though, you should prolly file a new one.
>
> Dunno, I've edited the file and removed the null characters.  Time will
> tell whether new ones will be logged or not.
>
>
> IIUC, syslog-ng handles rotating the logs.  Do I need to do something to
> make it rotate them?

syslog-ng, as long as I remember, has never rotated its logs. You need logrotate (or something similar) to do it for you.

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México