On 03/09/2016 10:46 PM, Andrei Borzenkov wrote:
10.03.2016 03:07, Greg Freemyer пишет:
The _netdev mounts were only attempted once and that was too soon. Another bug?
May be. For some reasons systemd explicitly does *not* add dependency on "fs_spec" for network mount points in this case. I.e. normally if you have
/foo/bar /mnt ...
it would implicitly add
RequiresMoountsFor=/foo/bar /mnt
I note from systemd.unit(5) RequiresMountsFor= Takes a space-separated list of absolute paths. Automatically adds dependencies of type Requires= and After= for all mount its required to access the specified path.
that orders it after any mount point that contains them.
But for network the former is skipped. It is sure something to at least ask upstream.
Or experiment to see what happens with specific versions of systemd. It's easy enough for Greg to experiment with. He can set the various combinations we've discussed each in turn and see what the generator produces by looking in /var/run/systemd/generator at the .mount files. I have mountable /home /anton /Photographs /By-year /2015 The mount units produced by the geneerator for each of those has an explicit "After". I would expect when the generator runs on the correctly configured fstab (as per earlier mail about _netdev not being on the loop entries as Carlos documents) to see something like that, perhaps a "Requires" . -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org