mirror of
https://github.com/samba-team/samba.git
synced 2025-01-11 05:18:09 +03:00
8b6f58194d
We should not double fork in notify mode or systemd think something during startup will be wrong and send SIGTERM to the process. So sometimes the daemon will not start up correctly. systemd will also handle the process group. BUG: https://bugzilla.samba.org/show_bug.cgi?id=13129 Signed-off-by: Andreas Schneider <asn@samba.org> Reviewed-by: Andrew Bartlett <abartlet@samba.org> Autobuild-User(master): Andrew Bartlett <abartlet@samba.org> Autobuild-Date(master): Tue Nov 28 15:31:27 CET 2017 on sn-devel-144 |
||
|---|---|---|
| .. | ||
| nmb.service | ||
| README | ||
| samba.conf.tmp | ||
| samba.service | ||
| samba.sysconfig | ||
| smb.service | ||
| winbind.service | ||
With systemd the /run or /var/run are tmpfs filesystems. This means the direcories required by samba need to be created during startup. This can be done with a config file for tmpfiles, see samba.conf.tmp. You need to copy this file to the directoy systemd-tmpfiles is looking for its config files e.g.: install -d -m 0755 /etc/tmpfiles.d/ install -m644 samba.conf.tmp /etc/tmpfiles.d/samba.conf If you're a packager don't forget to run the systemd-tmpfiles binary in the script after samba has been installed. This makes sure the directory exists and you can start samba directly after the installation. /usr/bin/systemd-tmpfiles --create /etc/tmpfiles.d/samba.conf