mirror of
https://github.com/samba-team/samba.git
synced 2025-02-23 09:57:40 +03:00
e93a716a98
For smb, if the smb.conf contains explicit bindings to the network interfaces, the service must wait till network interfaces are up, otherwise the service won't be operational. The 0e571054a61e commit and the BZ 13184 have fixed this for nmb and samba, so do exactly the same here, for smb. BUG: https://bugzilla.samba.org/show_bug.cgi?id=13559 Signed-off-by: Oleksandr Natalenko <oleksandr@redhat.com> Reviewed-by: Andreas Schneider <asn@samba.org> Reviewed-by: Alexander Bokovoy <ab@samba.org> (cherry picked from commit a3d248f284eb2e5f4fe886310e481b28c9f1c392)
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