On Wed, 2009-01-14 at 13:30 -0700, Rob Crittenden wrote: > Brian Kosick wrote: > > Hi All, > > > > Sorry for the top post but I wanted to put the solution first... > > It turns out that I need to lay off the crack pipe a little bit. As > > soon as I added --ghost to the correct place everything started working > > fine. This was a little frustrating as everything that I found on the > > Net seemed to indicate that the --ghost option goes in the wrong place. > > > > Example: I WAS trying combinations of this, which doesn't work. > > > > dn: cn=internal,ou=auto.software,dc=corp,dc=example,dc=com > > cn: internal > > objectClass: automount > > automountInformation: -soft,intr,nodev,tcp,ro nfs.example.com:/var/qa > > --ghost > > > > It works just fine when you add it here: > > > > dn: cn=/software,ou=auto.master,dc=corp,dc=example,dc=com > > objectClass: automount > > cn: /software > > automountInformation: > > ldap:qapxe.qa.mxlogic.com:ou=auto.software,dc=corp,dc=example,dc=com > > --ghost > > > > I apologize for wasting everyones time, > > Apologize!? Heck, thanks for tracking this down! > > Do you know if this works without the ldap syntax in > automountInformation? E.g. can you use just: > > automountInformation: auto.software --ghost > > cheers > > rob <snip> Hrrm I don't know. From my understanding of how it works, wouldn't that be using LDAP to point back to the local /etc/auto.software file? Or just break it entirely? I can probably give it a try a little later... Brian
