On Fri, 2009-02-20 at 16:03 -0800, Rajouri Jammu wrote: > Hi, > > I'm again running into problem with cascaded automounts.
What sort of problem? > > This time I'm using the autofs as part of CentOS 5.0 > rpm -qa | grep autofs > autofs-5.0.1-0.rc2.43.0.2 That's a really old version considering the amount of development that has happened in v5. > > >Using the patch requires a configure option to be specified. > >I'm not sure if this patch has been added to the RHEL-4 package, > you'll > >need to check. In RHEL-5 the configure option is used when the > package > >is built so CentOS 5 will have this already > > Does autofs-5.0.. version have "--disable-mount-locking" configured by > default? Yes. > > Any suggestions would be of great help. > > Thanks! > > Ranjit > > > On Sun, Apr 20, 2008 at 6:50 AM, Ian Kent <[email protected]> wrote: > > On Sat, 2008-04-19 at 10:52 -0700, Rajouri Jammu wrote: > > Thank you for the prompt response. > > > > > > Yes, I'm using autofs4 which came with CentOS release 4.6 > > > RHEL-4 U6 should be OK. > But I don't think any of the versions of mount are 100%. > > > > > > > mount -V > > mount: mount-2.12a > > > > > > > > Is that version of mount OK or do I need a newer version to > work with > > the locking path? > > If I need a newer version can you please let me know > approximately > > which one? > > > > > > Lastly, does autofs5 not have this issue? > > > This is a problem with mount and any version of autofs that > uses /etc/mtab will have this problem. > > The later revisions of autofs v4 and autofs v5 use /etc/mtab > somewhat > less and so are less vulnerable. > > Using the patch requires a configure option to be specified. > I'm not sure if this patch has been added to the RHEL-4 > package, you'll > need to check. In RHEL-5 the configure option is used when the > package > is built so CentOS 5 will have this already. > > Ian > > > > _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
