From: James Pearson <james-p@moving-picture.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
nfs@lists.sourceforge.net, autofs@linux.kernel.org
Subject: Re: Re: [autofs] Server/client mismatch over status of a mount ...
Date: Mon, 17 Feb 2003 15:57:58 +0000 [thread overview]
Message-ID: <3E510686.6899E7BE@moving-picture.com> (raw)
In-Reply-To: shsheb2lxde.fsf@charged.uio.no
So, is there a possible workround?
Thanks
James Pearson
Trond Myklebust wrote:
>
> >>>>> " " == H Peter Anvin <hpa@zytor.com> writes:
>
> > Automount doesn't tell the server anything. It's possible that
> > /bin/umount has this bug, however.
>
> That is correct. In the util-linux implemention of 'umount' the RPC
> call is done before the actual syscall.
> My guess is that this was decided upon in order to avoid races for the
> case where some other process does another 'mount'.
>
> Cheers,
> Trond
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-02-17 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 14:06 Server/client mismatch over status of a mount James Pearson
2003-02-17 15:20 ` [autofs] " H. Peter Anvin
2003-02-17 15:50 ` Trond Myklebust
2003-02-17 15:57 ` James Pearson [this message]
2003-02-17 16:16 ` Trond Myklebust
2003-02-17 17:49 ` James Pearson
2003-02-18 16:57 ` James Pearson
2003-02-19 9:56 ` H. Peter Anvin
2003-02-19 10:16 ` Trond Myklebust
2003-02-19 13:58 ` Ion Badulescu
2003-02-19 18:16 ` H. Peter Anvin
2003-02-20 3:20 ` Jeremy Fitzhardinge
2003-02-20 3:26 ` Ion Badulescu
2003-02-20 3:43 ` Jeremy Fitzhardinge
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=3E510686.6899E7BE@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=autofs@linux.kernel.org \
--cc=hpa@zytor.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.