On Fri, 2008-10-31 at 17:28 +0900, Ian Kent wrote: > On Fri, 2008-10-31 at 19:10 +1100, Paul Wankadia wrote: > > On Fri, Oct 31, 2008 at 7:02 PM, Ian Kent <[EMAIL PROTECTED]> wrote: > > > > > But I don't get a syntax error for the input that your mail specifies. > > > > If you make with flex --debug, what output do you see when automount starts? > > No debug info at all.
Oh .. it writes to stderr ... ha, I need to run in foreground. Anyway, this is what I see: lookup_nss_read_master: reading master files auto.master parse_init: parse(sun): init gathered global options: (null) lookup_read_master: lookup(file): read entry /hom --(end of buffer or a NUL) --accepting rule at line 139 ("/") --accepting rule at line 187 ("/") --accepting rule at line 187 ("h") --accepting rule at line 187 ("o") --accepting rule at line 187 ("m") --accepting rule at line 165 (" ") --accepting rule at line 289 ("/") --accepting rule at line 289 ("e") --accepting rule at line 289 ("t") --accepting rule at line 289 ("c") --accepting rule at line 289 ("/") --(end of buffer or a NUL) --accepting rule at line 289 ("a") --(end of buffer or a NUL) --accepting rule at line 289 ("u") --(end of buffer or a NUL) --accepting rule at line 289 ("t") --(end of buffer or a NUL) --accepting rule at line 289 ("o") --accepting rule at line 289 (".") --(end of buffer or a NUL) --accepting rule at line 289 ("h") --(end of buffer or a NUL) --accepting rule at line 289 ("o") --(end of buffer or a NUL) --accepting rule at line 289 ("m") --(end of buffer or a NUL) --accepting rule at line 289 ("e") --(end of buffer or a NUL) --(end of buffer or a NUL) --accepting rule at line 275 ("") --(end of buffer or a NUL) --EOF (start condition 0) master_do_mount: mounting /hom > Debug is possibly disabled in the package build. > I'll need to investigate. > > > > > Honestly, I have no idea why it scans a DNSTR for me, but as I > > mentioned, I have to work around it by escaping 'c' and 'o' with > > backslashes. When were those lex rules last modified? > > Yes, this part of the lex code has had recent changes so there's every > chance it is a bit broken or possibly flex is working differently > between our machines. > > Ian > > > _______________________________________________ > autofs mailing list > autofs@linux.kernel.org > http://linux.kernel.org/mailman/listinfo/autofs _______________________________________________ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs