From: Jim Rees <rees@umich.edu>
To: Sven Geggus <lists@fuchsschwanzdomain.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS4: ssh + unlink(~/.Xauthority) delays
Date: Tue, 21 Aug 2012 08:59:05 -0400 [thread overview]
Message-ID: <20120821125905.GA16550@umich.edu> (raw)
In-Reply-To: <k0vgkt$mm0$1@ultimate100.geggus.net>
Sven Geggus wrote:
Hello,
I'm about to setup a Linux based fileserver for home directories and a
couple of Linux clients with kerberos and NFS4 (no NFS3 for security
reasons).
The whole stuff is currently based on debian stable (with a backported
current NFS userland 1.2.5) and a recent vanilla kernel (3.5.2).
So far I have the NFS4 Server up and running as well as a couple of clients
with NFS4+autofs mounted home directories.
All this stuff mostly works now, but unfortunately I ran into some strange
bahaviour now.
When I ssh from one machine to another the system hangs (a delay of up to 60
seconds) while running xauth.
Replacing xauth by a wrapper script I have been able to trace this behaviour
to a hang of an unlink("/home/<user>/.Xauthority") system call.
So the question is what cases hangs in NFS4 based Linux systems in general
an in this particular case?
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`
next prev parent reply other threads:[~2012-08-21 12:59 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 ` Jim Rees [this message]
2012-08-21 16:04 ` NFS4: ssh + unlink(~/.Xauthority) delays Sven Geggus
2012-08-21 17:07 ` Jim Rees
2012-08-21 18:03 ` Malahal Naineni
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=20120821125905.GA16550@umich.edu \
--to=rees@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=lists@fuchsschwanzdomain.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).