Univention Bugzilla – Bug 43721
"log file = /var/log/samba/log.%m" without function
Last modified: 2019-01-03 07:23:24 CET
root@ucs-5140:/etc/samba# vim local.conf [global] log file = /var/log/samba/log.%m does not work as expected - "testparm -sv" shows the option: [global] ... log file = /var/log/samba/log.%m ... But in the filesystem you see: root@ucs-5140:/var/log/samba# ls -lah insgesamt 17M drwxr-x--- 3 root root 4,0K Feb 25 09:47 . drwxr-xr-x 22 root root 4,0K Feb 24 12:26 .. drwx------ 5 root root 4,0K Nov 9 21:05 cores -rw-r--r-- 1 root root 0 Nov 9 21:05 log. -rw-r--r-- 1 root root 36K Feb 25 09:48 log.%m ... All events are logged there. The test environment has a master and a backup running at the time of setting the option. (10.200.6.100 and 10.200.6.101)
Upstream bug, see URL.
Workaround may be using a memberserver with univention-samba installed: # univention-install univention-samba # vim /etc/samba/local.conf [global] log file = /var/log/samba/log.%m logging = yes # ucr commit /etc/samba/* # service samba restart # testparm -sv # root@ucs-8180:/var/log/samba# ls -lah insgesamt 24K drwxr-x--- 3 root root 4,0K Jan 26 09:44 . drwxr-xr-x 13 root root 4,0K Jan 25 15:12 .. drwx------ 5 root root 4,0K Jan 26 09:44 cores ... -rw-r--r-- 1 root root 0 Jan 26 09:44 log.wb-UCS-8180 ...
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.