On Wed, 2007-01-24 at 13:13 -0600, Bill Maloy wrote: > >From <http://docs.sun.com/app/docs/doc/816-0211/6m6nc676n?a=view> > "The network or subnet component is preceded by an at-sign (@). " > > This feature does not play nicely with autofs-5.0.1-rc3. > > In the host_match() function within lib/rpc_subs.c, the > initial character of the formal parameter named "pattern" > is compared against '@' ... indicating a need to check > the NFS client's hostname (myname) for membership > in the given netgroup. > > However, the existing "if/else-if" logic does not > consider the case where a network address (and mask) > follows the '@' character -- instead of an "expected" > netgroup name. > > You can confirm this behavior by modifying the access > control list of a working v5 automounting export > (containing an @netgroup specification) to have > a Solaris-like @network/mask specifier, instead. > > The fix? Well, if the innetgr() function supported > "IPaddress/mask"-style strings in addition to netgroup > names, the code as written would probably support > access_lists containing network components. > > Until that day, the character following the '@' sign > in an exports list item could be examined. If numeric, > the masked_match() logic of the 'else' branch could > be used. If non-numeric, the existing innetgr() > logic would be used.
No, that won't work. According to the reference above a network name can contain any printable character and so could itself be numeric. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
