You are not logged in.
I am using openbox without desktop environment, Thunar as file manager.
I am using NFS share on a laptop, over the net (ethernet).
The client is my desktop.
Currently I mount it manually by it's mount point:
$ mount /mnt/pinkLaptopDeclared by /etc/fstab line like that:
pinkLaptop:/shareName /mnt/pinkLaptop nfs4 _netdev,defaults,noauto,user 0 0Now if that pink laptop turned off by a mistake before I managed to umount this mount,
every attempt to umount it now will hang the shell and Thunar fails to launch at all untill I reboot my desktop.
Is there any way to make Thunar/GVFS manage hot-plugging of that NFS mount like it does with flash disks and the like?
In addition to that, when I look at the Devices sector in the Thunar's side pane
I see that GVFS mountable volumes appears grey-out then I can click to mount them, and when so they have a little button to unmount them.
Unlike mounts of fstab auto mounts (I have some NTFS partitions mounted at every boot) that appears there with none of these features.
Is it true to say that currently in my setup GVFS not handling fstab entries? Is it could?
If it is of any help, I paste here my .xinitrc:
xcompmgr &
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fiand my /etc/X11/xinit/xinitrc.d/30-dbus that runs dbus and openbox:
if [ -z "$DBUS_SESSION_BUS_ADDRESS" ] && type dbus-launch >/dev/null; then
eval $(dbus-launch --sh-syntax --exit-with-session openbox-session)
fiI want to use GVFS in it's "Ideal" way. Am I have some mistakes here?
Last edited by Florax (2013-12-24 15:46:48)
English is not my native language.
Offline
I have a similar issue, maybe it's the same problem.
My NAS exports a few shares via NFS that I pick up on my computers. Now the NAS goes to sleep at night but if I don't close Thunar before the NAS goes to sleep and NFS shares become un-available it hangs Thunar!
Here's an example of how the shares are mounted, from /etc/fstab
# nas1 server
nas1:/c/home /media/nas1/home nfs noauto,x-systemd.automount,x-systemd.device-timeout=120 0 0Any idea on how to make Thunar give up more quickly on those shares? Is there another way to mount those shares in Thunar instead of using x-systemd.automount?
Thanks,
Headed for the second star to the right and straight on 'til morning...
Schultzter
Offline
As an FYI, I've changed my /etc/fstab to look like this:
nas1:/c/home /media/nas1/home nfs noauto,user,_netdev,timeo=1800 0 0I did this because all the shares were showing up twice in Thunar, once with the device icon and again with a network folder icon.
Now they only show up once, and only mount when I click on them. But sometimes Thunar times out before they have a chance to be mounted and I need to click a few times before it works. My NAS spins down the disks during in-activity so I guess it's kind of normal but I hoped the timeo=1800 would be long enough for the NAS to spin-up and respond. But I get the impression that Thunar ignores that time-out option.
I need to test again more thoroughly but I don't think Thunar is hanging any more if I have it open after the NAS has gone to sleep for the evening.
Headed for the second star to the right and straight on 'til morning...
Schultzter
Offline