On Thu, 2007-11-01 at 11:16 +0100, Xiwen Cheng wrote: > Recently we migrated from static nfs mounts to autofs on our webserver. > This concerns all /home/*/public_html/ directories which are mounted > read-only by default. /etc/autofs/auto.home includes some exceptions > whereas certain users requested their ~/public_html or even ~/ to be > writable. > > This setup works _almost_ all the time although syslog reveals some > extremely strange behaviors, a snippet: > > Oct 31 17:38:02 host1 automount[14335]: mount(nfs): nfs: mount failure > nfs.somewhere.com:/home/user/.bash_profile/public_html on > /home/user/.bash_profile/public_html > > There are numerous similair failures including normal webserver > requests. The above sample was the result of a "su - user" if anyone > wonders. > > The big question mark is: Why does autofs try to mount ~/public_html one > threshold/level lower? It shouldn't look any further than > /home/anyuser/public_html. > ~/public_html > > Server info > =========== > OS: 2.6.19-gentoo-r5 > net-fs/nfs-utils: 1.0.12-r1 > net-libs/libnfsidmap: 0.19
Strange you report the versions of these but not autofs, being the package your asking about. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
