From: Chris Wagner <wagnerc@plebeian.com>
To: cygwin@cygwin.com
Subject: Re: find command seems to lock files
Date: Mon, 26 Aug 2019 01:57:00 -0000 [thread overview]
Message-ID: <26a08c26b5acb89631981fc69425446a@plebeian.com> (raw)
In-Reply-To: <CA+7cx1rwShfSJYJZdvSF-8ERaAQqcYxtQquKKB8xwoBxqhLVog@mail.gmail.com>
On 2019-08-19 8:33 am, Morten Kjærulff wrote:
> find //$server/d$/dir/subdir*/subsubdir -name 'thefile' -printf '%A+\n'
>
> Problem is that it seems this command locks thefile, as the application
> sometimes can't delete it.
Unfortunately, yes. On Windows, a "full stat" requires that the file be
opened.
This is why Perl has the ${^WIN32_SLOPPY_STAT} flag variable.
https://metacpan.org/pod/distribution/perl/pod/perlvar.pod#${^WIN32_SLOPPY_STAT}
> ${^WIN32_SLOPPY_STAT}
>
> If this variable is set to a true value, then stat() on Windows will
> not try to open the file. This means that the link count cannot be
> determined and file attributes may be out of date if additional
> hardlinks to the file exist. On the other hand, not opening the file is
> considerably faster, especially for files on network drives.
>
-Chris
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-08-25 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 12:49 Morten Kjærulff
2019-08-19 14:06 ` Corinna Vinschen
2019-08-19 14:13 ` Eliot Moss
2019-08-19 14:26 ` Corinna Vinschen
2019-08-19 14:41 ` Morten Kjærulff
2019-08-19 15:03 ` Eliot Moss
2019-08-19 17:05 ` Andrey Repin
2019-08-19 17:21 ` Andrey Repin
2019-08-19 17:41 ` Morten Kjærulff
2019-08-19 18:52 ` Eliot Moss
2019-08-19 19:43 ` Greywolf
2019-08-21 19:53 ` L A Walsh
2019-08-26 1:57 ` Chris Wagner [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=26a08c26b5acb89631981fc69425446a@plebeian.com \
--to=wagnerc@plebeian.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).