From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: xemacs@cs.uiuc.edu, bug-gnu-emacs@prep.ai.mit.edu, ding@ifi.uio.no
Subject: Re: NFS/Emacs bug
Date: Tue, 4 Jun 1996 13:14:33 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.960604131102.24080A-100000@is> (raw)
In-Reply-To: <rjvih8y88a.fsf@kleene.dina.kvl.dk>
On 3 Jun 1996, Per Abrahamsen wrote:
> When using `directory-files' on large directories (5000+ files) the
> answer is sometimes truncated, like this:
>
> (length (directory-files "~/Mail/ding/list"))
> ==> 2287
> (length (directory-files "~/Mail/ding/list"))
> ==> 5460
>
> This has been reproduced with Linux and Solaris as NFS clients and
> with SGI and Solaris as NFS servers. It has also been reproduced with
> Emacs 19.30, Emacs 19.31, and XEmacs 19.13.
`directory-files' (on dired.c) tests the directory entries returned by
`readdir' to be non-empty, by using the `DIRENTRY_NONEMPTY' macro. That
macro looks at the inode returned in dp->d_ino, and if it's zero, the
entry is considered empty. I suggest stepping through the loop that
calls `readdir' with a debugger to see whether maybe under that specific
combination of NFS servers and clients, the inode is sometimes reported
as 0 when it shouldn't have been.
prev parent reply other threads:[~1996-06-04 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-03 19:53 Per Abrahamsen
1996-06-04 11:14 ` Eli Zaretskii [this message]
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=Pine.SUN.3.91.960604131102.24080A-100000@is \
--to=eliz@is.elta.co.il \
--cc=bug-gnu-emacs@prep.ai.mit.edu \
--cc=ding@ifi.uio.no \
--cc=xemacs@cs.uiuc.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 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).