embedded spaces in automounter map options field
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have a situation that requires me to have embedded spaces in the options field of my automounter map. To make things trickier, the map has to be generated with an executable map. I am using shfs and have to use it's cmd mount option to force it to connect using a specific private key file. This requires there to be embedded spaces in the options field, like this:
- -fstype=shfs,cmd="ssh -i /usr/keys/<username> <username>@<host>"
Which causes the automounter to complain bitterly. Most of the information I've found is for having spaces in share names or mount points, but the advice given doesn't work in the options field. I've tried all kinds of quotes, backslashing, etc. I'd greatly appriciate help.
Please CC me on replies as I am not subscribed to the list.
--Geoff Mishkin <[email protected]>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBIhFXpH0X57UnVFoRAoChAJ9oQGxmeQse0iwBmmi6DlrSo6CziQCgyJ62 TiVrjLCwWxaFLvjs2wVZIKQ=
=aOwF
-----END PGP SIGNATURE-----
Ian Kent
maintainerQuoted 9 lines · Geoff Mishkin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1I have a situation that requires me to have embedded spaces in the options field of my automounter map. To make things trickier, the map has to be generated with an executable map. I am using shfs and have to use it's cmd mount option to force it to connect using a specific private key file. This requires there to be embedded spaces in the options field, like this:
Quoted 8 lines
- -fstype=shfs,cmd="ssh -i /usr/keys/<username> <username>@<host>"
Which causes the automounter to complain bitterly. Most of the information I've found is for having spaces in share names or mount points, but the advice given doesn't work in the options field. I've tried all kinds of quotes, backslashing, etc. I'd greatly appriciate help.
Please CC me on replies as I am not subscribed to the list.
You don't say which version of autofs you are using?
Ian
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It's autofs version 4.1.3.
--Geoff Mishkin <[email protected]>
Quoted 19 lines · you
Quoted 18 lines · Geoff Mishkin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1I have a situation that requires me to have embedded spaces in the options field of my automounter map. To make things trickier, the map has to be generated with an executable map. I am using shfs and have to use it's cmd mount option to force it to connect using a specific private key file. This requires there to be embedded spaces in the options field, like this:
- -fstype=shfs,cmd="ssh -i /usr/keys/<username> <username>@<host>"
Which causes the automounter to complain bitterly. Most of the information I've found is for having spaces in share names or mount points, but the advice given doesn't work in the options field. I've tried all kinds of quotes, backslashing, etc. I'd greatly appriciate help.
Quoted 5 lines
Quoted 1 line
Please CC me on replies as I am not subscribed to the list.
You don't say which version of autofs you are using?
Ian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBI2GYpH0X57UnVFoRAm4pAJ4lmMn2c3Z0i1sHqEg39zlEhjVf3QCfWtlO nWWAmp6dNEY/HYgKtQNzcjQ=
=YPe4
-----END PGP SIGNATURE-----
Ian Kent
maintainerQuoted 4 lines · Geoff Mishkin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1It's autofs version 4.1.3.
OK. That sounds bad.
I'll check it out soon as I can.
Ian
Ian Kent
maintainerQuoted 10 lines · Geoff Mishkin
Quoted 10 lines
Quoted 10 lines
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1I have a situation that requires me to have embedded spaces in the options field of my automounter map. To make things trickier, the map has to be generated with an executable map. I am using shfs and have to use it's cmd mount option to force it to connect using a specific private key file. This requires there to be embedded spaces in the options field, like this:
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
- -fstype=shfs,cmd="ssh -i /usr/keys/<username> <username>@<host>"
Which causes the automounter to complain bitterly. Most of the information I've found is for having spaces in share names or mount points, but the advice given doesn't work in the options field. I've tried all kinds of quotes, backslashing, etc. I'd greatly appriciate help.
On second thoughts if you are willing to try a patch then do this.
From the autofs v4 directory on kernel.org obtain the patches:
autofs-4.1.3-strict.patch
autofs-4.1.3-mtab_lock.patch
autofs-4.1.3-non_block_ping.patch
autofs-4.1.3-bad_chdir.patch
and then apply the attached patch and let me know how it goes.
Ian
modules/mount_nfs.c +1 -1
@@ -347,7 +347,7 @@int local, err;int nosymlink =0 ; -debug (MODPREFIX " root=%s name=%s what=%s, fstype=%s, options=%s" , +debug (MODPREFIX "root=%s name=%s what=%s, fstype=%s, options=%s" , root, name, what, fstype, options); whatstr =alloca (strlen (what) +1 );
modules/parse_sun.c +44 -23
99 lines not on this page · raw message
_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs
program mount problem
In reply to Ian KentI just installed 4.1.3 with the autofs4-2.4.22-20040508.patch. I have a server with 10 mount points and I only have permission to mount 1. If I cd to one I don't have permission to, I get permission denied in the syslog, but it will keep 'looping' the name of the mount.
the mount is /n3 - a program mount
the server is ns16 - 10 mounts exported
no permissions to mount e
cd /n3/ns16/e/n3/ns16/e/n3/ns16/e/n3/ns16/e/
At end, I hit tab for file completion and will loop /n3/ns16/e over and over - were it would just stop at one /n3/ns16/e with autofs-4.1.0. I am running redhat 7.3 and a 2.4.26 kernel.
Signature · 7 lines
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Rhythm & Hues 5404 Jandy Place Los Angeles, CA 90066 Voice: 310 448-7763 Fax: 310 448-7600 [email protected]
[email protected]
maintainerRe: program mount problem
Quoted 9 lines · Greg Bradner
I just installed 4.1.3 with the autofs4-2.4.22-20040508.patch. I have a server with 10 mount points and I only have permission to mount 1. If I cd to one I don't have permission to, I get permission denied in the syslog, but it will keep 'looping' the name of the mount.
the mount is /n3 - a program mount
the server is ns16 - 10 mounts exported
no permissions to mount e
Quoted 5 lines
cd /n3/ns16/e/n3/ns16/e/n3/ns16/e/n3/ns16/e/
At end, I hit tab for file completion and will loop /n3/ns16/e over and over - were it would just stop at one /n3/ns16/e with autofs-4.1.0. I am running redhat 7.3 and a 2.4.26 kernel.
Could you get some debug log output please.
Ian
Re: program mount problem
Option change.
I was using -v to get the version of automount in order to load different auto_master files. I didn't notice yesterday it failed on booting. I noticed it today when adding the --verbose and --debug. Changed it to --version. And it works. I was also looking at an old automount(8) man page.
Thanks and sorry for the false alarm.
Quoted 22 lines · [email protected] wrote:
Quoted 12 lines · Greg Bradner
I just installed 4.1.3 with the autofs4-2.4.22-20040508.patch. I have a server with 10 mount points and I only have permission to mount 1. If I cd to one I don't have permission to, I get permission denied in the syslog, but it will keep 'looping' the name of the mount.
the mount is /n3 - a program mount
the server is ns16 - 10 mounts exported
no permissions to mount ecd /n3/ns16/e/n3/ns16/e/n3/ns16/e/n3/ns16/e/
At end, I hit tab for file completion and will loop /n3/ns16/e over and over - were it would just stop at one /n3/ns16/e with autofs-4.1.0. I am running redhat 7.3 and a 2.4.26 kernel.
Could you get some debug log output please.
Ian
Signature · 7 lines
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Rhythm & Hues 5404 Jandy Place Los Angeles, CA 90066 Voice: 310 448-7763 Fax: 310 448-7600 [email protected]