Dear sirs:

[Please reply directly to <[EMAIL PROTECTED]>, as I am not on this
mailing list.]

While attempting to build an "executable map" for autofs, I discovered
a small but important bug in the manual page autofs(5).  The text (in
autofs version 3.1.7, as distributed with Red Hat Linux 8.0) reads:

   Executable Maps
       A  map  can  be  marked as executable.  The init script that parses the
       auto.master map will pass this as a program map to the automounter.   A
       program  map  will  be  called as a script with the key as an argument.
       The script needs to return one line of a map or no output at all if the
       key cannot be matched.

The last sentence is incorrect.  In reality, the script needs to
return *one line of a map, but with the first field (the key)
deleted*.

This error wasted a considerable amount of my time, and I hope you can
fix it in the next release.

In addition, I think it would be helpful if you could expand
README.options a bit.

First, it would be helpful to note that the autofs binary uses a
library of modules, so autofs *must be installed* in the location it
was built for before it can be executed.

Second, it would be helpful if there were an option to ./configure
that compiled and linked autofs with symbols and without optimization
(-g -O0), which is what one wants for debugging.  I found that I had
to do a considerable mount of hand editing of Makefiles to generate a
binary with a symbol table.

I suspect that both of these tasks are straightforward, but for a
naive user like me, there are no pointers to how to go about them.

Thank you for your consideration,

Dale
_______________________________________________
autofs mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/autofs

Reply via email to