Hi,
I added a smb share to my fstab. I tried various parameters in fstab, e.g.
//192.168.0.7/public /home/marvin/odroid cifs guest 0 0
or
//192.168.0.7/public /home/marvin/odroid cifs guest,x-systemd.requires=network.target,x-systemd.automount,x-systemd.device-timeout=10,x-systemd.idle-timeout=1min 0 0
The share mounts without issue, but during shutdown or reboot I get "a stop job is running" for 91sec.
Anyone an idea, how to avoid the that behavior?
I have seen this
https://bugs.debian.org/cgi-bin/bugr...cgi?bug=798314
which I tried
and this
https://www.kubuntuforums.net/showth...job+is+running
I added a smb share to my fstab. I tried various parameters in fstab, e.g.
//192.168.0.7/public /home/marvin/odroid cifs guest 0 0
or
//192.168.0.7/public /home/marvin/odroid cifs guest,x-systemd.requires=network.target,x-systemd.automount,x-systemd.device-timeout=10,x-systemd.idle-timeout=1min 0 0
The share mounts without issue, but during shutdown or reboot I get "a stop job is running" for 91sec.
Anyone an idea, how to avoid the that behavior?
I have seen this
https://bugs.debian.org/cgi-bin/bugr...cgi?bug=798314
which I tried
and this
https://www.kubuntuforums.net/showth...job+is+running






Usually in forums the word root "necro" is a reference to necromancy, bringing old threads back from the dead, but here I'm wondering what you mean. If you're disparaging your original question, no, not at all, IMO it's very valuable that questions like yours get asked.
Comment