From: "Capelle Benoît" <capelle@labri.fr>
To: autofs@linux.kernel.org
Subject: [PATCH] no-slashify-colons option
Date: Fri, 8 Dec 2006 14:13:03 +0100 [thread overview]
Message-ID: <200612081413.04075.capelle@labri.fr> (raw)
Hi,
After upgrading one of our servers from Fedora 5 (autofs-4.1.4) to Fedora 6
(autofs-5.0.1) we noticed that the "--no-slashify-colons" option was no more
working.
We've got the following maps.
/etc/auto.master:
/nfs /etc/auto.nfs --no-slashify-colons
/etc/auto.nfs:
datas -async,ro,bg,vers=3,tcp,timeo=600,hard,intr,rsize=32768,wsize=32768,context=system_u:object_r:httpd_sys_content_t
nfs_server:/exported_nfs
Setting log level to debug showed that the last colon from
system_u:object_r:httpd_sys_content_t (used for SELinux) was replaced by a
slash.
Dec 4 16:47:41 client automount[2094]: lookup_mount: lookup(file):
deptinfo -> -async,ro,bg,vers=3,tcp,timeo=600,hard,intr,rsize=32768,wsize=32768,context=system_u:object_r:httpd_sys_content_t
nfs_server:/exported_nfs
Dec 4 16:47:41 client automount[2094]: parse_mount: parse(sun): expanded
entry: -async,ro,bg,vers=3,tcp,timeo=600,hard,intr,rsize=32768,wsize=32768,context=system_u:object_r/httpd_sys_content_t
nfs_server:/exported_nfs
Using "--no-slashify-colons" should prevent this as it was back in version
4.1.4.
Following patch fixes the issue. Regards.
--
Benoit
diff -ur a/lib/master_tok.l b/lib/master_tok.l
--- a/lib/master_tok.l 2006-12-06 15:10:08.000000000 +0100
+++ b/lib/master_tok.l 2006-12-06 15:17:30.000000000 +0100
@@ -91,6 +91,7 @@
OPTIONSTR ([\-]?([[:alpha:]_]([[:alnum:]_\-])*(=([[:alnum:]_\-])+)*)+)
MACROSTR (-D{OPTWS}([[:alpha:]_]([[:alnum:]_\-])*)=([[:alnum:]_\-])+)
+SLASHIFYSTR (--(no-)?slashify-colons)
NUMBER [0-9]+
DNSERVSTR1 ([[:alpha:]][[:alnum:]\-.]*(:[0-9]+)?:)
@@ -323,6 +324,11 @@
{OPTWS} {}
+ {SLASHIFYSTR} {
+ strcpy(master_lval.strtype, master_text);
+ return(OPTION);
+ }
+
{MACROSTR} {
strcpy(master_lval.strtype, master_text);
return(OPTION);
reply other threads:[~2006-12-08 13:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612081413.04075.capelle@labri.fr \
--to=capelle@labri.fr \
--cc=autofs@linux.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.