> Am 11.09.2016 um 21:30 schrieb Martin Waschbüsch (mar...@waschbuesch.de)
> :
>
> Hi all,
>
> From what I could find out, SOGo does not do anything about its log file when
> reacting to SIGHUP.
> When logrotate moves the current logfile /var/log/sogo/sogo.log to
> /var/log/sogo/sogo.log.1, the file handle is kept open which makes SOGo
> continue to log messages to /var/log/sogo/sogo.log.1.
> I guess this is the reason for the logrotate script to contain the
> 'copytruncate' directive.
>
> Anyway, Would it be possible to override the function
> handle_SIGHUP(int signum)
> (in sope/sope-appserver/NGObjWeb/WOWatchDogApplicationMain.m)
> to take care of this?
>
> Alternatively, is it possible to configure SOGo to log to syslog? I could not
> find an option in the current documentation.
Anyone? Or should I open a bug report with this?
Thanks,
Martin
signature.asc
Description: Message signed with OpenPGP using GPGMail