> While the rest of my system is just cherry, I have not yet been able
> to solve the problem of why an NFS mount and associated binds don't
> work unless and until I wait a minute or two after the system comes
> up [...]
Sounds like the normal 90-second NFS grace period to me -- a feature,
On Fri 13 May 2016 at 07:28:50 (-0400), Dan Ritter wrote:
> On Fri, May 13, 2016 at 06:57:10AM -0400, Steve Matzura wrote:
> > On Fri, 13 May 2016 05:12:56 -0400, you wrote:
> >
> > >The options field in fstab should include "_netdev" for devices
> > >which cannot be mounted until networking is
On Fri, May 13, 2016 at 06:57:10AM -0400, Steve Matzura wrote:
> On Fri, 13 May 2016 05:12:56 -0400, you wrote:
>
> >The options field in fstab should include "_netdev" for devices
> >which cannot be mounted until networking is stable.
>
> I have never heard of that option. I'll try it and
Dan,
On Fri, 13 May 2016 05:12:56 -0400, you wrote:
>The options field in fstab should include "_netdev" for devices
>which cannot be mounted until networking is stable.
I have never heard of that option. I'll try it and report back. Now,
what about the lines for the binds that immediately
On Fri, May 13, 2016 at 03:34:44AM -0400, Steve Matzura wrote:
> While the rest of my system is just cherry, I have not yet been able
> to solve the problem of why an NFS mount and associated binds don't
> work unless and until I wait a minute or two after the system comes
> up, then issue a
While the rest of my system is just cherry, I have not yet been able
to solve the problem of why an NFS mount and associated binds don't
work unless and until I wait a minute or two after the system comes
up, then issue a 'mount -a'. I have tried putting 'mount -a' into
/etc/init.d/rc.local, and
6 matches
Mail list logo
