On Sat, 2011-06-18 at 00:29 +0100, David Howells wrote:
Hi Ian,
At the top of autofs4_d_automount() you have:
/* The daemon never triggers a mount. */
if (autofs4_oz_mode(sbi))
return NULL;
I think this should be returning -EISDIR. If by some chance we do get
On Sat, 2011-06-18 at 01:11 +0100, David Howells wrote:
autofs4_d_automount() returns 0 if it detects that the calling process is in
Oz
mode (ie. it's the autofs userspace daemon). This return, however, is meant
to
indicate to follow_automount() that the caller should retry the check on
On Fri, 2011-06-17 at 15:12 +0100, James Pearson wrote:
I using CentOS 5 on a large number of boxes with a NIS indirect
automount map.
I've been using the following syntax in /etc/auto.master:
/mntpointyp:custom.map
And this has worked fine for ages
Recently, I wanted to provide
On Fri, 2011-06-17 at 10:40 -0400, Jimmy Dorff wrote:
Hello,
I'm attempting to migrate an existing (and working) nis automount system
to ldap. We have several layers of nested maps and I'm attempting to
recreate that in LDAP.
# Automount master for /foo
dn: cn=/foo,
On Fri, 2011-06-17 at 16:40 -0400, Jimmy Dorff wrote:
On 06/17/2011 10:40 AM, Jimmy Dorff wrote:
# here is my attempt at nesting another level
dn: cn=project, ou=auto.phy,dc=phy,dc=duke,dc=edu
objectClass: automount
cn: project
automountInformation: ldap
Ian Kent wrote:
Any idea why autofs fails to read entries from the included NIS map when
the creation date of the map mount point is in the future? - but works
fine when the same NIS map is referenced directly from /etc/auto.master?
Don't know about the timestamp but there were some
On Sat, 2011-06-18 at 21:08 +0100, James Pearson wrote:
James Pearson wrote:
Sorry, I should have said - this is CentOS 5.5 with autofs
5.0.1-0.rc2.143.el5_5.6 - and I've also tried it with
5.0.1-0.rc2.143.el5_6.2 - with the same result.
It is easy to reproduce - with an included
