From: Marcus Alanen <marcus.alanen@abo.fi>
To: "-rb (Robert T. Brown)" <rbrown@netmentor.com>
Cc: linux-kernel@vger.kernel.org, maalanen@abo.fi
Subject: Re: getcwd() returning -ENOENT???
Date: Sun, 08 Feb 2004 00:34:22 +0200 [thread overview]
Message-ID: <402567EE.3050804@abo.fi> (raw)
In-Reply-To: <40255AE4.6010007@netmentor.com>
-rb (Robert T. Brown) wrote:
> Greetings.
> I have 2 clients and a server. On one client, every 24-72 hours
> I get into a situation where the shells cd'ed into
> my [automounted] home directory report:
>
> gretchen@falcon{11}pwd
> pwd: cannot get current directory: No such file or directory
I've had this exact same thing. I start konsole and write "pwd",
resulting in an error message. Merely cd:ing again "fixes" it, as you
have also noted. My home directory was mounted over NFS. This was on a
Fedore 1 machine with their kernel. The mountpoint was not automounted,
however.
I wrote a C program whose only purpose was to print the current working
directory using getcwd(3). Immediately after starting konsole, the
program failed every time; after cd:ing it started working.
I can't unfortunately remember any further details like exact glibc or
kernel version, and I've also lost any strace or tcpdump from that time
as well. The problem was extremely persistent for a week or so, then
suddenly stopped occurring. And I think neither the NFS server nor the
client was rebooted in between.
You might want to try dumping the traffic and checking with ethereal
what is actually sent across the wire, in both directions.
Marcus
next prev parent reply other threads:[~2004-02-07 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 21:38 getcwd() returning -ENOENT??? -rb (Robert T. Brown)
2004-02-07 22:34 ` Marcus Alanen [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-07 15:03 Russell King
2000-12-07 15:31 ` Alexander Viro
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=402567EE.3050804@abo.fi \
--to=marcus.alanen@abo.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=maalanen@abo.fi \
--cc=rbrown@netmentor.com \
/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