• cenzorrll@piefed.ca
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    1 day ago

    I’m not great at any init things, but systemd has made my home server stuff relatively seamless. I have two NASs that I mount, and my server starts up WAY faster than both of them, and I (stupidly) have one mount within the other. So I set requirements that nasB doesn’t mount until nasA has, then docker doesn’t start until after nasB is mounted. Works way better than going in after 5 minutes and remounting and restarting.

    Of course, I did just double my previous storage on A, so I could migrate all of Bs stuff back. But that would require a small amount of effort.

      • cenzorrll@piefed.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 hours ago

        I have a wait-for-ping service that pings nas A, once it gets a successful response it tries to mount.

        I lifted it from a time when I needed to ping my router because Debian had a network-online service bug. I adapted it to my nas because the network-online issue eventually got fixed and mounting my shares became the next biggest issue.

        It seems like this person might have grabbed that same fix for what I eventually did because our files are…oddly almost exactly the same.

        https://cweiske.de/tagebuch/systemd-wait-nfs.htm

        • WhyJiffie@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          2 hours ago

          thanks!

          do you perhaps also have a solution for hanging accesses to network mounts when the server is inaccessible?