25.03.2018 12:18, Michael Hirmke пишет:
Hi,
[...]
systemctl show upnp\x2droot\x2dremote-VDR_Videos.mount var-spool-video-video0.mount would be good start.
they differ in a few entries:
------------------------< snip snip snip >----------------------------- [...] < Result=exit-code ---
Result=success [...] < After=network.target remote-fs-pre.target -.mount systemd-journald.socket system.slice network-online.target < RequiresMountsFor=/upnp-root-remote
After=system.slice network-online.target systemd-journald.socket remote-fs-pre.target -.mount nfs-server.service network.target RequiresMountsFor=/var/spool/video [...] < NeedDaemonReload=yes
NeedDaemonReload=no [...] ------------------------< snip snip snip >-----------------------------
The difference for After= can explain the different behaviour on boot.
Actually it does not. nfs-server.service should not have any impact on remote mount (unless you do loopback mount from the same host, but your error is different).
Are you using wicked or NetworkManager?
I'm using wicked. With NetworkManager on my Tumblewed systems I also had problems, but could solve them using dispatcher scripts. For wicked I didn't find such a thing.
But both entries are created by systemd-fstab-generator.
It is possible to extend generated units as well. Start with "systemctl cat var-spool-video-video0.mount nfs-server.service" to check drop-ins for these units.
Ok.
So the question keeps the same: Why is systemd treating both entries different?
This is side question (only out of curiosity). The actual question is -
Can/should I recreate them by deleting them and running generator again?
As I suggested, first check with "systemctl cat" where configuration comes from. Before and After are not transitive - they must be defined in one of two units.
what is needed to ensure name resolution is available when NFS are mounted on boot. It depends on your configuration. Normal way to do it is to order remote mounts after nss-lookup.target. Your log entries suggest that you are running local resolver daemon; if it is used for local name resolution you need additionally order nss-lookup.target after it.
named is used for local name resolution, too - indeed.
named on Leap 42.3 still is an init script 8-< How would I solve this? As far as I know, there is no feature like Before= for init scripts. Do I have to create a systemd service for named instead?
initscript is still unit (actually, in current systemd generator creates native unit definition out of initscript) so you can use standard ways 1. systemctl edit - it allows you to edit drop-in file for a unit - *any* unit actually. This drop-in is persistent and is merged into unit definition when systemd reads definition. 2. You can add x-systemd.requires=named.service (or whatever is it called) to /etc/fstab options. This is equivalent to both Requires and After in generated mount unit. Note that it is more strong than simple After; it is up to you to decide what is appropriate. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org