Mateusz Guzik <[email protected]> wrote
  in <[email protected]>:

mj> On Sun, Nov 18, 2012 at 07:43:25AM +0900, Hiroki Sato wrote:
mj> > Chris Rees <[email protected]> wrote
mj> >   in <cadlo839wqzapenuqdovpq74yjcmkpqncekpvs_n9xnwmlrk...@mail.gmail.com>:
mj> >
mj> > ut> On 2 November 2012 14:21, Eitan Adler <[email protected]> wrote:
mj> > ut> > On 2 November 2012 09:56, Chris Rees <[email protected]> wrote:
mj> > ut> >> I'll take a look.
mj> > ut> >
mj> > ut> > untested:
mj> > ut>
mj> > ut> Based on Eitan's patch, I've tested this one, and documented it in 
mount(8) too:
mj> > ut>
mj> > ut> http://www.bayofrum.net/~crees/patches/mountonlylate.diff
mj> > ut>
mj> > ut> Does anyone have any suggestions/objections/urge to approve it?
mj> >
mj> >  Is the original problem due to backgrounding of NFS mount only?  If
mj> >  so, implementing prevention of duplicate invocation into mount(8)
mj> >  would be more reasonable, I think.
mj> >
mj>
mj> We have 2 distinct scripts that try to mount same set of filesystems.
mj> I think this is the real bug here and proposed patches makes it go away in
mj> an IMHO acceptable way.

 I just wanted to make sure if the case is limited to background NFS
 mount or not.

 rc.d/mountlate just tries to mount the filesystems that are not
 mounted yet at that time in addition to the "late" ones, not always
 to mount the same set twice.  If it is a bug, it is better to simply
 fix -l to exclude not-yet-mounted ones without "late" keyword than
 adding another option.

-- Hiroki

Attachment: pgpUIIqBlLUpq.pgp
Description: PGP signature

Reply via email to