From: Neil Brown <neilb@suse.de>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: nfs@lists.sourceforge.net, Jan Rekorajski <baggins@sith.mimuw.edu.pl>
Subject: Re: RELEASE CANDIDATE - nfs-utils-1.1.0-rc1
Date: Mon, 2 Apr 2007 09:35:29 +1000 [thread overview]
Message-ID: <17936.16833.295258.406430@notabene.brown> (raw)
In-Reply-To: message from Frank van Maarseveen on Sunday April 1
On Sunday April 1, frankvm@frankvm.com wrote:
> On Thu, Mar 29, 2007 at 07:31:25PM +1000, Neil Brown wrote:
> >
> > Hmm... good question.
> >
> > I think:
> >
> > - idmapd and gssd should be started before any nfs mount
> > - idmapd and svcgssd should be started before nfsd
> > - mountd should start before nfsd.
>
> At first that seems the logically correct order but suppose a client
> succeeds in mounting something but issues NFS requests before nfsd got
> started on the server?
That shouldn't matter. The NFS server will not respond so the client
will retry.
Ofcourse if you have a soft mount it could get messy, but then soft
mounts are always messy.
>
> where's the exportfs?
Good point. exportfs should be run before mountd is started, and
after nfsd filesystem is mounted.
NeilBrown
>
> Consider a "sleep 30" at every point in the startup sequence and think
> about what would go wrong. Also consider a dead-again server at every
> point in the startup sequence.
>
> --
> Frank
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-04-01 23:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 4:12 RELEASE CANDIDATE - nfs-utils-1.1.0-rc1 Neil Brown
2007-03-29 8:44 ` Jan Rekorajski
2007-03-29 9:31 ` Neil Brown
2007-03-29 12:44 ` Jan Rekorajski
2007-03-29 14:20 ` Trond Myklebust
2007-03-29 16:35 ` J. Bruce Fields
2007-03-29 16:45 ` Talpey, Thomas
2007-03-29 14:24 ` Trond Myklebust
2007-03-29 14:30 ` Talpey, Thomas
2007-04-01 12:16 ` Frank van Maarseveen
2007-04-01 23:35 ` Neil Brown [this message]
2007-04-01 12:04 ` Frank van Maarseveen
2007-03-29 9:51 ` Bernd Schubert
2007-03-30 2:19 ` Neil Brown
2007-03-30 10:44 ` Bernd Schubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17936.16833.295258.406430@notabene.brown \
--to=neilb@suse.de \
--cc=baggins@sith.mimuw.edu.pl \
--cc=frankvm@frankvm.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.