Comment on systemd has been a complete, utter, unmitigated success

Eryn6844@piefed.blahaj.zone ⁨2⁩ ⁨days⁩ ago

• Eggymatrix@sh.itjust.works ⁨2⁩ ⁨days⁩ ago

  I dont know what you are doing, but I have my smb shares simply in fstab and never heard of any .mount file

  source

  • avidamoeba@lemmy.ca ⁨2⁩ ⁨days⁩ ago

    On modern systems, fstab entries are read by systemd and .mount files are automatically created for each entry. 😄

    source

    • Eryn6844@piefed.blahaj.zone ⁨2⁩ ⁨days⁩ ago

      i am making them in salt-stack systemd templates/pillars. i will see what i miss when i do a fstab one.

      source
  • bjoern_tantau@swg-empire.de ⁨2⁩ ⁨days⁩ ago

    Systemd can use .mount files to make services and stuff depend on the availability of a mount. They can either be created by hand or are created automatically from fstab.

    source
• Zwuzelmaus@feddit.org ⁨2⁩ ⁨days⁩ ago

  IIRC You simply write/change the fstab as in every system. Then you say “systemctl daemon-reload” once, and this (re)creates your .mount files. Then “mount -a” or whatever you need.

  source
• darcmage@lemmy.dbzer0.com ⁨2⁩ ⁨days⁩ ago

  wiki.archlinux.org/title/Samba#As_systemd_unit

  That’s the guide I followed on my desktop and laptop.

  source

  • Eryn6844@piefed.blahaj.zone ⁨2⁩ ⁨days⁩ ago

    thanks,

    source
• avidamoeba@lemmy.ca ⁨2⁩ ⁨days⁩ ago

  Network not ready by time the mount is executed?

  source

  • Eryn6844@piefed.blahaj.zone ⁨2⁩ ⁨days⁩ ago

    yup,

    source

    • tinsuke@lemmy.world ⁨2⁩ ⁨days⁩ ago

      I have a service that pings the server:

      cat <<EOF | sudo tee /etc/systemd/system/ping-smb.service
      [Unit]
      Description=Blocks until pinging 192.168.1.10 succeeds
      After=network-online.target
      StartLimitIntervalSec=0
      
      [Service]
      Type=oneshot
      ExecStart=ping -c1 192.168.1.10
      Restart=on-failure
      RestartSec=1
      
      [Install]
      WantedBy=multi-user.target
      EOF
      
      sudo systemctl enable ping-smb.service
      

      And then I make the fstab entry depend on it:

      x-systemd.requires=ping-smb.service
      

      source

      • avidamoeba@lemmy.ca ⁨2⁩ ⁨days⁩ ago

        I had something similar when I used to mount an NFS share. I had a bash line that would loop ping and then mount once ping succeeds. Having a separate service that pings and making the mount dependent on it is probably the better thing to do. Should also work when put in Requires= in a .mount file.

        source
• Eryn6844@piefed.blahaj.zone ⁨2⁩ ⁨days⁩ ago

  thanks everyone.

  source
• hesh@quokk.au ⁨2⁩ ⁨days⁩ ago

  Can you see if its trying and failing by using journalctl?

  source

  • Eryn6844@piefed.blahaj.zone ⁨2⁩ ⁨days⁩ ago

    no matter what i do it only does on try.

    source
• caseyweederman@lemmy.ca ⁨2⁩ ⁨days⁩ ago

  My nfs mounts always add 1:45 to my boot even though I added _netdev to their lines in fstab. I don’t get it.

  source

  • FauxLiving@lemmy.world ⁨2⁩ ⁨days⁩ ago

    Use

    _netdev,nofail,x-systemd.device-timeout=10s
    

    nofail doesn’t interrupt the boot and 10 seconds is a more sane timeout. You can also use

    x-systemd.automount
    

    And it will automatically mount the directory the first time it is accessed.

    source