32

I'm working on a systemd .service script that is supposed to start after a CIFS network location is mounted via /etc/fstab to /mnt/ on boot-up.

The script waits for an OpenVPN dependency script to launch first, but I also want it to wait for mount to complete.

/etc/systemd/system/my-daemon.service:

[Unit]
Description=Launch My Daemon
After=network.target vpn-launch.service
Requires=vpn-launch.service

I tried to add systemd.mount to the line: After=network.target vpn-launch.service systemd.mount, but it didn't give the results I was hoping for.

  • Does it work if you add systemd-remount-fs to your After list? – Eric Renouf Dec 4 '15 at 19:13
39
+50

a CIFS network location is mounted via /etc/fstab to /mnt/ on boot-up.

No, it is not. Get this right, and the rest falls into place naturally.

The mount is handled by a (generated) systemd mount unit that will be named something like mnt-wibble.mount. You can see its actual name in the output of the systemctl command. You can look at it in detail just like any other unit with systemctl status.

Very simply, then: you have to order your unit to be started after that mount unit is started.

After=network.target vpn-launch.service mnt-wibble.mount

Further reading

  • 9
    List mounts with "systemctl list-units --type=mount" – nijave Apr 5 '18 at 17:10
  • For followers, "wibble" is just a dummy name, like "foobar" – rogerdpack Jul 5 at 17:03
16

Sorry but I can't comment yet.

Like JdeBP said, you should be ordering on the filesystem mount. You can predict the name of the mount unit or, alternatively, you can use (in unit section):

RequiresMountsFor=/absolute/path/of/mount

This option creates the dependencies to the appropriate *.mount units to make the path accessible before starting the service. It may not be on all systemd versions, but I've been using it in a CentOS 7 machine for the last 6 months or so.

14

Although both answers are correct, I want to add my two cents to the discussion, because when I have looked for it I was missing some instructions and examples of how to proceed.

  1. Add the filesystem to /etc/fstab
  2. Type mount -a which mounts all filesystems mentioned in fstab
  3. Look for the systemd unit that has been generated with:

    systemctl list-units | grep '/path/to/mount' | awk '{ print $1 }'

    (should return something that ends with .mount)
  4. Add the found mount-unit to the After= statement in the *.service file

Here is an example of starting the my-daemon service on boot but after the network is ready, a CIFS share is mounted at /mnt/cifs, and the vpn-launch service has started:

/etc/fstab

//servername/sharename /mnt/cifs cifs defaults,some,other,options 0 0

Note: You may want to add nofail to your fstab options (e.g. when using an external drive). Otherwise, your machine won't boot if the device is not connected. See ArchWiki's fstab article


/etc/systemd/system/my-daemon.service

[Unit]
Description=Launch My Daemon
Requires=vpn-launch.service mnt-cifs.mount
After=network.target vpn-launch.service mnt-cifs.mount

[Service]
ExecStart=/path/to/my-daemon

[Install]
WantedBy=multi-user.target

Do not forget to enable the service such that it is started on boot: systemctl enable my-daemon

Note that this works for other filesystems (NFS, HDDs, etc.) as well.

As already mentioned, both answers are correct and I encourage everybody to read them but for me a couple of examples would have saved me some time.

Update (2019-06-25):

  • added a note regarding fstab options to prevent boot lock when using external drives
  • added mnt-cifs.mount to the Requires= list which causes the my-daemon.service fail to start-up when the cifs mount was not successfully mounted
1

@bm-bergmotte: thanks for your instruction which helped me a lot. For me it´s just working, if I put

After=network.target vpn-launch.service mnt-cifs.mount
Requires=vpn-launch.service mnt-cifs.mount

If I don´t put "mnt-cifs.mount" inside the "Requires" (and in this order) it works for reboot/ startup, but the service starts anyway, if the device is not mounted. After putting it additionally inside ""Requires" the service mounts the device before starting it, if the device was not mounted.

  • You are right. If the mount fails then the my-daemon.service is started anyway. After= just dictates the order. Requires= makes it mandatory that the cifs mount must be present (see Sufiyan Ghori answer on that one). I'll update my answer. – bm-bergmotte Jun 25 at 16:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.