The Samba-Bugzilla – Bug 12935
No reliable way to reopen samba.log on an system without systemd
Last modified: 2017-07-25 19:50:11 UTC
As mentioned in the debian bugreport #803924 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803924) an restart of the samba service is necessary to make it write to samba.log after an logrotation.
I'm running 4.6.6 on debian wheezy (build without systemd support). Sending an SIGHUP to the samba parent process with pid from /var/run/samba/samba.pid here in logrotates postrotate section does not work, the processes are still writing to /var/log/samba/log.samba.1 here until the samba-ad-dc service got restarted.
So I wrtite this report to request the "smbcontrol reopen-logs" extension to fix this issue on systems without systemd.
Thanks in advance,
Have you tried the logrotate's "copytruncate" option?
Or, by hand
cp log.samba log.samba.1
(In reply to Giulio from comment #1)
Great tip. Logrotation works fine with copytruncate.
Thank you very much Giulio!