Univention Bugzilla – Bug 44138
Additionally to samba/autostart we also need to set nmbd/autostart
Last modified: 2020-07-04 11:53:43 CEST
Additionally to samba/autostart we now also need to set nmbd/autostart. Details: 1.a) Before systemd, on systems with univention-samba the /etc/init.d/samba script controlled both smbd and nmbd, depending only on samba/autostart. But on all systems (also the univention-samba4 ones) /etc/init.d/nmbd only considers nmbd/autostart. 1.b) On systems running univention-samba4 the /etc/init.d/samba script is not a UCR template and doesn't consider samba/autostart. Instead, it calls the individual scripts /etc/init.d/nmbd, /etc/init.d/smbd and /etc/init.d/samba-ad-dc which each consider different UCR variables: * /etc/init.d/samba-ad-dc : samba4/autostart * /etc/init.d/nmbd : nmbd/autostart * /etc/init.d/smbd : smbd/autostart # on samba4 this script doesn't do anything 2) With systemd, the association between variable name and service is done via the .univention-service files. +++ This bug was initially created as a clone of Bug #43470 +++
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.
We need to fix samba4.service for systemd anyway: - make samba4.service as meta unit (e.g. similar to postgresql.service), which does not start any services. - define samba-ad.service, nmbd.service, smbd.service, ... and make them PartOf=samba4.service, so systemd can track the services individually but users still can start/stop Samba4 as one service. - user proper Before/After/Depends= between those individual services. Bug #44139 is for nmbd.service