Systemd dependencies and boot order
Solution 1
Use systemctl edit smb.service
to update the dependencies.
After=dirsrv.target
- Will ensure the smb.service is started after dirsrv.target.
For robustness, (which will be worth while if you're tinkering with this stuff) you may also wish to include some of the following:
Requires=dirsrv.target
- Activate dirsrv.target when smb.service is activated. Will cause smb.service to fail if dirsrv.target fails.
Wants=dirsrv.target
- Activate dirsrv.target when smb.service is activated. Won't cause smb.service to fail if dirsrv.target fails.
BindsTo=dirsrv.target
- If dirsrv.target is deactivated, deactivate smb.service.
Source: http://www.freedesktop.org/software/systemd/man/systemd.unit.html
systemd-ui
provides a GUI for systemd. Gives a good view of the state of systemd but you'll still have to use a text editor to modify the unit files.
Solution 2
Do two things:
-
Edit the
/lib/systemd/system/smb.service
unit file, to specify the dependency. The[unit]
section contains anAfter=
line which specifies what services/targets should be reached before this one.After=syslog.target network.target nmb.service winbind.service
Change it to:
After=dirsrv.target syslog.target network.target nmb.service winbind.service
Report this dependency back to Fedora as a bug, so that it can be incorporated in future releases.
Solution 3
you maybe need to change or include a line with the Requires
directive in the [Unit]
section of the /usr/lib/systemd/system/smb.service
file.
Requires=dirsrv.target
and
After=dirsrv.target
Solution 4
There are two alternatives to modifying the service file in /usr/lib/systemd/system
(see Example 2. Overriding vendor settings):
Copy the file to
/etc/systemd/system
and perform the modifications on the copy. This file will completely override the file in/usr/lib
.Create the file
/etc/systemd/system/smb.service.d/local.conf
. The contents of the file should be something like the example below. This selectively overrides the "Requires" and "After" options in the vendor provided service file.
Each of these (including modifying the file in /usr/lib
) offers advantages and disadvantages. The best choice may depend on the service and the nature of the modifications.
While it may work, it is not sufficient to only add the "After" option (see [Unit] Section Options). "After" controls order, but not dependencies. If dirsrv.target
is not started in some other way, specifying an order will not start it. Use of the "Requires" or "Wants" option will force dirsrv.target
to be started.
[Unit]
Requires=dirsrv.target
After=dirsrv.target
NB: I don't know if this approach was available when this question was originally asked.
Related videos on Youtube
Dylan Klomparens
Updated on September 18, 2022Comments
-
Dylan Klomparens over 1 year
I need to specify a boot order for processes to start. I have 389 Directory Server and Samba running on Fedora 18. How can I have the network services boot, then 389 DS, then Samba? Is there a GUI to manage this in Fedora?
I have enabled Samba to start with
systemctl enable smb.service
. I have also enabled 389 DS withsystemctl enable dirsrv.target
.-
vonbrand about 11 yearsSystemd doesn't require order among services, the idea is to start everything in parallel and hand the conections to the servers as they become available. The configuration given by the default installation should be fine. Why do you think you have to define an order? Does something fail to work?
-
mat over 6 years@vonbrand I had this problem, where my DHCP server needed slapd to be up (because its configuration was stored in an LDAP directory). If it wasn't, the DHCP server wouldn't come up.
-
-
Dylan Klomparens about 11 yearsThat doesn't seem to work. Samba is still booting before 389.
-
galaxy almost 10 yearsWell, I've voted for this answer, however, I'd personally go with Wants=dirsrv.target instead of Requires=. (see systemd.unit(5) for Wants=)
-
scottysseus almost 9 yearsafter you modify
unit
files, you should usually runsystemctl daemon-reload
-
John Wang over 7 yearsIn a case A Requires B , what will say "B" has "failed" so that A will not be started? The program of B return a Non-zero value?
-
Jeremy Visser about 5 yearsThanks for editing the answer! It resolves concerns, and I have converted to an upvote. :-)