> On Mon, 29 Mar 2004, Rainer Krienke wrote:
> > This outputs eg something like
> >
> > -fstype=nfs,hard,intr,nodev,nosuid,nonstrict,rsize=8192,wsize=8192 \
> > /export/user serverhost:/export/user
> > .....
> >
> > So there are options, a qouted newline and then the map entry without
> > the key.
Hmmm, the daemon code that handles executable maps likes to see
[-mount-options] [mapkey] mapreferent
([] indicating optional), whereas the file map handler wants
mapkey [-mount-options] mapreferent
It's rather surprising that the mapkey is legal in the middle position -- I
would expect it to always be in the same place and to never be optioal -- I
can understand that it's mandatory in a file map, and if it were forbidden
in an executable map, but optional?
I suspect that the ugly parser code never even looks at it; the parser uses
the last whitespace-separated field as the referent, and the first or
second as the mount options, depending on the type of map and whether the
field beings with a hyphen.
In any case, a comment in the man page (even if not representing the
parser's complete range of behavior bug for bug :-) would be helpful for
people writing executable maps. Answering Reiner's first question, I said,
"what's it likely that /sbin/automount needs to know? Either an imitation
file map (wrong, rejected), or the same minus the key (acceptable when I
tried it)."
That also ties in with the formst which you would get with a NIS map if you
could get NIS maps to work on your system. (I haven't worked on that one
for a long time; maybe it's fixed in recent updates and I can lose the
executable home map.)
James F. Carter Voice 310 825 2897 FAX 310 206 6673
UCLA-Mathnet; 6115 MSA; 405 Hilgard Ave.; Los Angeles, CA, USA 90095-1555
Email: [EMAIL PROTECTED] http://www.math.ucla.edu/~jimc (q.v. for PGP key)
_______________________________________________
autofs mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/autofs
