You are not logged in.
Hello,
I've had a nas (synology) with nfs shares I used to automount via systemd via this fstab line :
server_ip:/volume1/homes/me/Documents /home/me/Documents nfs user,hard,nolock,noauto,comment=systemd.automount,nofail
I thought this automounting would permit to start my arch while the nas if offline, provided I don't try to access /home/me/Documents
But no, it doesn't work well :
* Thunar won't start (more exactly, it will start only when the mount is done)
* 'ls ~' waits infinitely and does not show anything
I realise this is probably a classic nfs issue but I've had not found the right query to get the solution.
Would you have any idea to solve this problem ?
Regards
Mikael
Last edited by jasonwryan (2012-09-24 07:02:34)
Offline
Pretty sure you need x-systemd.automount there:
https://wiki.archlinux.org/index.php/Systemd#Automount
Offline
Thanks, but I changed my fstab according to this while keeping my nas offline : still the same problem.
systemctl :
home-mikael-Documents.automount loaded active running home-mikael-Documents.automount
home-mikael-Documents.mount loaded active mounted /home/mikael/Documents
Regards
Mikael
Offline
Try adding intr to your fstab line.
See 4.3.1 here.
You're just jealous because the voices only talk to me.
Offline
Thanks again, but still nothing better.
Regards,
Mikael
Offline
I issued this command :
$ cat /proc/mounts
...
systemd-1 /home/mikael/Documents autofs rw,relatime,fd=16,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
...
And after running the following command, things got better (ls works, thunar starts) :
# systemctl stop home-mikael-Documents.automount
Seems like systemd is not compatible with my goals.
Regards,
Mikael
Offline
Please do not prepend [Closed] to your threads; if it is solved, use that term. Closed means that the thread can no longer be posted in.
Offline