On Wed, 2025-12-10 at 12:12 -0500, pgnd wrote: > > > It seems that my problem is because I also have bridging set up on this > > > machine. Apparently the network appears ready way too early. > > > > Yeah, I've looked into this before. It turns out that "just wait until > > the network is up" is one of those very difficult things that appears > > easy at *first*... > > tho it's not a universal fit for nfs mounts, autofs does a nice job of > behaving itself re: network 'up' for nfs use > > its deps > > [Unit] > Description=Automounts filesystems on demand > After=network.target ypbind.service sssd.service network-online.target > remote-fs.target rpc-statd.service rpcbind.service > Wants=network-online.target rpc-statd.service rpcbind.service > > are a good starting point > > ( that said, i've added 'sleep xx' to units more than once !)
network-online.target is where a lot of the dragons are hidden these days, if you look into its actual implementation. :D The systemd docs say "By default all remote mounts defined in /etc/fstab make use of this service", so if you find a case where adding an explicit dep on network-online.target makes an fstab mount work that wasn't working before, that sounds like it's probably a bug. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected] https://www.happyassassin.net -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
