Hrrrm thanks, I believe that it is an unresolved bug, based on the info regarding this issue that I've already found via google.... It looks like the autofs author back in 2006 came _real close_ to looking into this, but a workaround seemed to have put this issue back into the deep dark corners of his mind. In fact he probably has dreams that he forgot about something to this day because of it. I'm joining the list to see if I can't get anyone to look into this.... Brian On Tue, 2009-01-13 at 17:27 -0700, Patrick Morris wrote: > On Tue, 13 Jan 2009, Brian Kosick wrote: > > > I should clarify... My original looked like this: > > > > dn: cn=internal,ou=auto.software,dc=corp,dc=mxlogic,dc=com > > cn: internal > > objectClass: automount > > automountInformation: -soft,intr,nodev,tcp,ro > > itchy.corp.mxlogic.com:/var/qa > > > > Which worked but I want to use the --ghost option so I tried.... > > > > dn: cn=internal,ou=auto.software,dc=corp,dc=mxlogic,dc=com > > cn: internal > > objectClass: automount > > automountInformation: -soft,intr,nodev,tcp,ro > > itchy.corp.mxlogic.com:/var/qa --ghost > > > > Which broke it. > > Brian > > As far as I know this is an unresolved bug in autofs's LDAP support. > > There may be workarounds depending on which OS/distribution you're on. > > -- > Fedora-directory-users mailing list > Fedora-directory-users@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-directory-users -- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
