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

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.

diff --git a/units/.gitignore b/units/.gitignore
index fe23b12266a81a56875efaee8fafa767363b316b..f969466bd782fe6eef032889695cf077cf354ae7 100644 (file)
--- a/units/.gitignore
+++ b/units/.gitignore
@@ -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

diff --git a/units/remote-fs.target.m4 b/units/remote-fs.target
similarity index 77%
rename from units/remote-fs.target.m4
rename to units/remote-fs.target
index 53054b6ec43bd4a7eecd9b855fe70b44b0fa2542..a48f87e5ddee2896abaca5524f7cccc7b5a435ae 100644 (file)
--- a/units/remote-fs.target.m4
+++ b/units/remote-fs.target
@@ -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