On Thursday 15 December 2011, Anton Aylward wrote:
Ruediger Meier said the following on 12/15/2011 07:44 AM:
On Thursday 15 December 2011, Anton Aylward wrote:
Are there some unit files created by the installation process? Perhaps that would be a better approach since they could be made dependent on the specific Ethernet port that leads to the NFS server being active.
The ethernet port which a specific nfs mount depend on cannot be set always staically. Dependencies are like this: server FQDN -> server IP -> route to server/client IP -> client ethernet port
The mount command itself invokes the DNS query to resolve the server name thus you can't know before what route and finally which port will be used.
Are you describing the dependency relationships that are explicitly made clear in the SystemD units and target or are you describing what is "hidden in the code" of the way pre-SystemD mount works?
No, just wanted to mention that in general nobody (including systemd) can't find out for sure which network device is needed to mount a specific NFS directory before actually trying to mount it. So your above idea "...they could be made dependent on the specific Ethernet port that leads to the NFS server ..." is IMO not possible. It has to be generic like "waiting for complete network setup" and then try nfs mount (hoping that there is a device to reach the server). Of course if admin knows what he is doing then he could replace the generic deps by more specific ones but no way to do this in systemd's default config. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org