picnoir/Systemd
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

remote-fs.target: do not order after network.target

Browse source 
remote-fs.target is ordered after the {auto,}mount units. In case of automount
we do not want to wait for the network to come up before proceeding. In case
of a regular mount unit, the unit will be ordered after network.target
so the behavior is unchanged.

This speeds up boot quite a bit for me when having some services needing
NetworkManager-wait-online.service, and having my home partition on nfs
under an automountpoint.
This commit is contained in:
Tom Gundersen 2011-06-11 15:55:11 +02:00 committed by Lennart Poettering
parent fbe092cc70
commit 54763e1266
2 changed files with 0 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
units/.gitignore vendored
View file

@ -31,7 +31,6 @@ systemd-random-seed-save.service
systemd-initctl.service
systemd-logger.service
getty@.service
remote-fs.target
systemd-update-utmp-runlevel.service
systemd-update-utmp-shutdown.service
test-env-replace

5
units/remote-fs.target.m4 → units/remote-fs.target
View file

@ -9,11 +9,6 @@
[Unit]
Description=Remote File Systems
m4_dnl
m4_ifdef(`FOR_SYSTEM',
m4_dnl When running in system mode we need the network up
After=network.target
)m4_dnl
[Install]
WantedBy=multi-user.target