Skip to contentSkip to conversation

Sample auto.net provided with autofs is incorrect

PATCH Paul Smith 2 participants 4 messages May 24, 2007 – Jun 6, 2007 Kernel automounter

lore
Share & tools
lore

Paul Smith

author
#0 lore raw

Hi all; I sent this on May 1 but I haven't seen it come through yet?

Please see this bug I just reported against Ubuntu:

https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/111612

I believe this problem also exists in the original autofs package. However, I can't seem to find the source anywhere; the freshmeat page for autofs looks quite out of date and doesn't have any homepage/etc. info, and Google searches came up empty as well.

I attach a patch below.

Signature · 5 lines
-----------------------------------------------------------------------------
 Paul D. Smith <[email protected]>                       http://netezza.com
 "Please remain calm--I may be mad, but I am a professional."--Mad Scientist
-----------------------------------------------------------------------------
      These are my opinions--Netezza takes no responsibility for them.
etc/auto.net renamed from etc/auto.net-dist +1 -1
@@ -37,7 +37,7 @@
 # Newer distributions get this right
 SHOWMOUNT="$SMNT --no-headers -e $key"
 
-$SHOWMOUNT | LC_ALL=C sort -u -k 1 | \
+$SHOWMOUNT | LC_ALL=C cut -d\  -f1 | LC_ALL=C sort -u | \
 	awk -v key="$key" -v opts="$opts" -- '
 	BEGIN	{ ORS=""; first=1 }
 		{ if (first) { print opts; first=0 }; print " \\\n\t" $1, key ":" $1 }

_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs

maintainer
#1 lore raw
Quoted 11 lines · Paul Smith

Hi all; I sent this on May 1 but I haven't seen it come through yet?

Please see this bug I just reported against Ubuntu:

https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/111612

I believe this problem also exists in the original autofs package. However, I can't seem to find the source anywhere; the freshmeat page for autofs looks quite out of date and doesn't have any homepage/etc. info, and Google searches came up empty as well.

Doesn't Ububtu record release version and package version against bugs? What is the version of autofs in Ubuntu?

Ian

author
#2 lore raw
Quoted 2 lines · Ian Kent

Doesn't Ububtu record release version and package version against bugs? What is the version of autofs in Ubuntu?

Hm I don't know why that's not there.

Anyway, the version of autofs in my Ubuntu (7.04) is:

ii autofs 4.1.4-13build1 kernel-based automounter for Linux

I just checked the 5.0.1 version (weird, I couldn't find it for anything the first time I looked!) and although auto.net has changed slightly, this problem still exists. On my system where showmount for one of my servers contains multiple entries for different hosts for the same partition, the output generated by auto.net has multiple entries for the same host.

maintainer
#3 lore raw
Quoted 9 lines · Paul Smith
Quoted 2 lines · Ian Kent

Doesn't Ububtu record release version and package version against bugs? What is the version of autofs in Ubuntu?

Hm I don't know why that's not there.

Anyway, the version of autofs in my Ubuntu (7.04) is:

Quoted 8 lines

ii autofs 4.1.4-13build1 kernel-based automounter for Linux

I just checked the 5.0.1 version (weird, I couldn't find it for anything the first time I looked!) and although auto.net has changed slightly, this problem still exists. On my system where showmount for one of my servers contains multiple entries for different hosts for the same partition, the output generated by auto.net has multiple entries for the same host.

Yes, but if you use 5.0.1 (and I recommend all the patches on kernel.org as well) then use the "-hosts" map instead, it shouldn't have this problem. Beware that, being new, it has been changed a number of times, the latest change being to drop the exports access control checking. This was the subject of a number of difficulties but in the end it was disabled because there isn't any way to make it work behind a NAT interface (oops and so obvious).

If you need to continue using version 4 then you'll need to persuade your platform support people to add a patch to resolve the issue. There will be a 4.1.5 at some point in the future but my focus is very much on version 5.

Ian