30.08.2013 16:07, JJ wrote:
Package: autofs
Version: 5.0.7-3ubuntu1
Severity: normal
Dear Maintainer,
I am trying to access an autofs mounted resource that depends on another autofs
managed resource.
I.e. I try to open a truecrypt container that is located on a samba fileshare.
Both are registered with autofs and both are initially not mounted.
When I try to access the truecrypt container it fails.
The autofs log says "no such file" for the cifs container and does not try to
mount the cifs resource automatically.
If I manually mount the cifs fileshare (or try to accesss this prior to the
truecrypt) it works.
After some research and communication with the autofs maintainer (Ian Kent)
I found out that in order for this to work autofs has to be configured with the
configure option
--disable-mount-locking is used.
Currently, autofs_5.0.7-3.debian does not use this option.
I contacted the autofs maintainer and he confirmed that
--disable-mount-locking should be used in the configure.
He believes that using this option causes no side effects and solves the issue.
I wonder why this isn't the default, or why the used-by-default
code ever exist.
Do you have pointers to the mentioned discussions?
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
