Re: Modern automounters and umount
On Mon 24 Feb 2020 at 10:54:28 (-0000), Curt wrote:
> On 2020-02-24, Mark Allums <maa@allums.com> wrote:
> >>
> >> How to set an environment variable in a DE is left as an exercise for
> >> the reader.
> >
> > The gvfsd --no-fuse doesn't do it for me.
> >
>
> That may be David's exercise then.
I think not. I made my suggestion (exactly a year ago) as I thought
the option, and its corresponding variable, could have been overlooked
on the man page, which was supposed to have been consulted already.
I also wrote on the next day that "Doesn't work" wasn't a response
that carried much information. It's therefore disappointing to read
"doesn't do it for me" this time around.
However, a later post contains:
george@martha:~$ gvfsd --no-fuse
bash: gvfsd: command not found
george@martha:~$ systemctl stop gvfsd
Failed to stop gvfsd.service: Unit gvfsd.service not loaded.
which suggests a bit of misunderstanding about what gvfsd is.
AIUI it's a daemon (hence the d), and not in anyone's PATH,
which is why you have to find out where it's running from and
what might be consulting the value of GVFS_DISABLE_FUSE.
Also I think the service is called gvfs-daemon (but there may
be other related ones involved).
As for doing exercises, I don't have gvfs* installed, nor any DE,
so I wouldn't know where to start.
Drifting a litle, I do remember being surprised how easy it is for
devices to be mounted twice, having had difficulty myself (mount
would complain the device was already mounted). It turned out that,
because the device I tried using was originally mounted readonly,
I also had to set ro in the second mount command for it to succeed.
Cheers,
David.
Reply to: