Skip to contentSkip to conversation

autofs breakage & fix

DISCUSSION Steve Thompson 3 participants 4 messages Dec 18, 2007 – Dec 20, 2007 Kernel automounter

lore
Share & tools
lore
#0 lore raw

FYI,

I upgraded an x86 CentOS 4.5 client system (autofs-4.1.3-199.3) to CentOS 4.6 (autofs-4.1.3-231), no other changes, and autofs broke. Maps come from an LDAP server, for example:

dn: cn=common,nisMapName=auto.xxx,dc=example,dc=org
objectClass: nisObject
cn: common
nisMapName: auto.xxx
nisMapEntry: server:/mnt/mda/data1/common -rw,rsize=32768,wsize=32768

When attempting to automount this, the client is passing the mount path, _including the options_, to the server as the path to be mounted, and the server of course says "no such file and directory". This works on 4.5.

If the nisMapEntry field is rewritten to put the options first:

nisMapEntry: -rw,rsize=32768,wsize=32768 server:/mnt/mda/data1/common

then it works on both versions of the OS. So something is less tolerant in parsing in 4.6.

Steve

#1 lore raw
Quoted 16 lines · Steve Thompson

FYI,

I upgraded an x86 CentOS 4.5 client system (autofs-4.1.3-199.3) to CentOS 4.6 (autofs-4.1.3-231), no other changes, and autofs broke. Maps come from an LDAP server, for example:

dn: cn=common,nisMapName=auto.xxx,dc=example,dc=org
objectClass: nisObject
cn: common
nisMapName: auto.xxx
nisMapEntry: server:/mnt/mda/data1/common -rw,rsize=32768,wsize=32768

When attempting to automount this, the client is passing the mount path, _including the options_, to the server as the path to be mounted, and the server of course says "no such file and directory". This works on 4.5.

Quoted 6 lines

If the nisMapEntry field is rewritten to put the options first:

nisMapEntry: -rw,rsize=32768,wsize=32768 server:/mnt/mda/data1/common

then it works on both versions of the OS. So something is less tolerant in parsing in 4.6.

From autofs(5):

FORMAT
key [-options] location

It's not that the new version is less tolerant, it's that the new version actually allows spaces in path names.

Cheers,
Jeff

#2 lore raw
Quoted 2 lines · Jeff Moyer

It's not that the new version is less tolerant, it's that the new version actually allows spaces in path names.

Ah, gotcha. Thanks,

-s

maintainer
#3 lore raw
Quoted 6 lines · Steve Thompson
Quoted 2 lines · Jeff Moyer

It's not that the new version is less tolerant, it's that the new version actually allows spaces in path names.

Ah, gotcha. Thanks,

And, while version 5 is mostly tolerant of this for maps, at some point the map parser will be re-written and probably won't be nearly as tolerant.

Ian