mirror of
https://github.com/samba-team/samba.git
synced 2024-12-23 17:34:34 +03:00
a1e78cc372
The only value this now provides is use of a notification script to log when start/stop are called. This was used for debugging strange start/stop failures, which have not been recently seen. Also, systemd does a good job of logging start/stop. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com> |
||
---|---|---|
.. | ||
ctdb.service.in | ||
nmb.service.in | ||
README | ||
samba.conf.tmp | ||
samba.service.in | ||
samba.sysconfig | ||
smb.service.in | ||
winbind.service.in |
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