All of lore.kernel.org
 help / color / mirror / Atom feed
From: Malahal Naineni <malahal@us.ibm.com>
To: Jim Rees <rees@umich.edu>
Cc: Sven Geggus <lists@fuchsschwanzdomain.de>, linux-nfs@vger.kernel.org
Subject: Re: NFS4: ssh + unlink(~/.Xauthority) delays
Date: Tue, 21 Aug 2012 13:03:53 -0500	[thread overview]
Message-ID: <20120821180353.GB4561@us.ibm.com> (raw)
In-Reply-To: <20120821170759.GA13076@umich.edu>

> Sven Geggus wrote:
> 
>   Jim Rees <rees@umich.edu> wrote:
>   
>   > No, the question is why did X put that file in your home directory.  That's
>   > not where it belongs.  I've got this in my .xinitrc:
>   > 
>   > setenv XAUTHORITY /tmp/Xauthority`id -u`
>   
>   I agree, that ~/.Xauthority is probably not the best place for this file,
>   but it is the default (at least in Debian).
>   
>   If it is expected behaviour that this will not work correctly with shared
>   Homedirectories, I wonder why this did not cause me any trouble with NFS3
>   for many years.

NFS3 doesn't have delegations and this file placement should not be an
issue in NFSv4 either if it is working correctly!

Regards, Malahal.


  reply	other threads:[~2012-08-21 18:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21  8:25 NFS4: ssh + unlink(~/.Xauthority) delays Sven Geggus
2012-08-21  9:19 ` NFS4ERR_DELAY (was: NFS4: ssh + unlink(~/.Xauthority) delays) Sven Geggus
2012-08-21 10:41   ` Jeff Layton
2012-08-21 12:52     ` NFS4ERR_DELAY Sven Geggus
2012-08-21 13:07       ` NFS4ERR_DELAY Jeff Layton
2012-08-21 17:47         ` NFS4ERR_DELAY J. Bruce Fields
2012-08-22  8:33           ` NFS4ERR_DELAY Sven Geggus
2012-08-21 12:59 ` NFS4: ssh + unlink(~/.Xauthority) delays Jim Rees
2012-08-21 16:04   ` Sven Geggus
2012-08-21 17:07     ` Jim Rees
2012-08-21 18:03       ` Malahal Naineni [this message]
2012-08-21 18:42         ` Jim Rees
2012-08-21 20:59           ` J. Bruce Fields

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=20120821180353.GB4561@us.ibm.com \
    --to=malahal@us.ibm.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lists@fuchsschwanzdomain.de \
    --cc=rees@umich.edu \
    /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.