Another try to explain:
mount.davfs and umount.davfs are designed to be mount and umount
helpers for the system's mount and umount program. The intention is to
make mounting a davfs2 file system behave as much as possible like any
other file systems. You usually mount with 'mount ' and
unmount wit
Well, I looked at the contents of /proc/mounts when a davfs2 share is
mounted, and the user_id option is there. That makes me doubt that
Werner's explanation is correct, or at least that it explains
everything.
Joey, did you use fuse or coda as the backend? fuse is the default so
if you don't k
Werner> umount(8) will search /etc/mtab for a matching entry and check
Werner> for option 'user='. /proc/mounts does not show this
Werner> option.
Does /proc/mounts not have a user_id= option for davfs2 mountpoints? It
does for those mounted with (packages linked to) libfuse.
Which leads to the
Hello Joey,
the error message originates from umount(8) not from umount.davfs. It
usually happens when your system lacks /etc/mtab or when /etc/mtab is
replaced by /proc/mounts.
You can use mount option 'users' instead of 'user' to work around the
problem. But 'users' will allow any user to unmoun
Package: davfs2
Version: 1.4.6-1.1
Severity: normal
I have davfs configured to allow a regular user to mount a filesystem:
joey@gnu:~>mount /media/box.com
joey@gnu:~>df /media/box.com
FilesystemSize Used Avail Use% Mounted on
https://www.box.com/dav/ 26G 13G 13G 50% /media
5 matches
Mail list logo
