On Mon, 29 Mar 2004, Jim Carter wrote: > > 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?
Umm. I'm going to have to check that. Seems to me that an executable map should be expected to emit the same map format as other maps. > > 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, Yep. Ian _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
