Zentyal Forum, Linux Small Business Server
Zentyal Server => Other modules => Topic started by: harlan on August 27, 2020, 05:26:09 am
-
I have a zentyal 6.2 community box running as the AD controller.
The stock /etc/samba/smb.conf contains:
log level = 3
log file = /var/log/samba/samba.log
max log size = 100000
and while /var/log/samba/samba.log will eventually rotate to /var/log/samba/samba.log.old, processes continue to write to the "old" file descriptor and eventually /var fills up.
My preference would be to let this rotation happen via logrotate, so I'd change the above stanza to "max log size = 0" and add suitable code to /etc/logrotate.d/samba but that doesn't work because a reboot causes a fresh /etc/samba/smb.conf to be installed, and then *both* log rotating systems try to work at the same time, and we *still* have processes that are trying to write to samba.log.old, which fills /var.
When /var fills, nobody can log in to the domain.
What's a good way to solve this problem?
I would really rather not automatically reboot zentyal once a week and as part of the boot sequence remove /var/log/samba/samba.log.old, as that could cause potentially useful information to be lost.