chiark / gitweb /
remote-fs.target: do not order after network.target
authorTom Gundersen <teg@jklm.no>
Sat, 11 Jun 2011 13:55:11 +0000 (15:55 +0200)
committerLennart Poettering <lennart@poettering.net>
Tue, 14 Jun 2011 15:30:46 +0000 (17:30 +0200)
commit54763e12662d465a038c424ea7baf565cca7be76
tree82732dcf6bde62a81c240caf3661efa92deb2c7b
parentfbe092cc70bd90af5fc2d746935b51f31a4cc629
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.
units/.gitignore
units/remote-fs.target [moved from units/remote-fs.target.m4 with 77% similarity]