From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Holger Kiehl <Holger.Kiehl@dwd.de>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Testing if a file or directory exist
Date: Sun, 9 Sep 2007 06:07:20 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0709090605220.31293@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0709090907400.18317@diagnostix.dwd.de>
On Sun, 9 Sep 2007, Holger Kiehl wrote:
> Hello
>
> What is the quickest way to test if a file or directory exist. I can
> think of three different system calls that can be used: access(),
> stat() and open(). Writting a little test program I found that this
> is also the order of which is the quickest, that is access() is the
> quickest and open() the slowest.
if all you want to do is check for existence, then, execution time
notwithstanding, you should use the method which accomplishes that and
nothing more, so the obvious solution would be stat().
it would be illogical to call open() since a side-effect would be that
you then had an open file. in short, if you just want to test, then
just test.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
next prev parent reply other threads:[~2007-09-09 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 9:26 Testing if a file or directory exist Holger Kiehl
2007-09-09 10:07 ` Robert P. J. Day [this message]
2007-09-09 10:16 ` Benoit Rouits
2007-09-09 15:04 ` LDB
2007-09-10 15:53 ` Holger Kiehl
2007-09-10 18:01 ` Glynn Clements
2007-09-09 13:15 ` Glynn Clements
2007-09-10 15:39 ` Holger Kiehl
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.LNX.4.64.0709090605220.31293@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=Holger.Kiehl@dwd.de \
--cc=linux-c-programming@vger.kernel.org \
/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).