From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Bruce Jerrick <bmj001@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: cygwin 3.5.3-1 : "Device or resource busy" from 'find {pagefile,swapfile}.sys'
Date: Thu, 4 Apr 2024 18:25:59 +0200 [thread overview]
Message-ID: <Zg7Ul25z75Z2YcnR@calimero.vinschen.de> (raw)
In-Reply-To: <e29f0d76-3b05-aa63-2e15-b2d5982d4410@gmail.com>
Hi Bruce,
On Apr 4 07:22, Bruce Jerrick via Cygwin wrote:
> As of cygwin 3.5.3-1, 'find' reports "Device or resource busy" and
> exits with status 1 on these two files:
>
> $ find /cygdrive/c/{pagefile,swapfile}.sys
> /cygdrive/c/pagefile.sys
> find: ‘/cygdrive/c/pagefile.sys’: Device or resource busy
> /cygdrive/c/swapfile.sys
> find: ‘/cygdrive/c/swapfile.sys’: Device or resource busy
>
> $ echo $?
> 1
Thanks for the report.
Should be fixed in cygwin-3.6.0-0.113.g38b513983590, which is
just being built and should be ready in an hour or two.
This will go into 3.5.4, of course.
Corinna
next prev parent reply other threads:[~2024-04-04 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 14:22 Bruce Jerrick
2024-04-04 16:25 ` Corinna Vinschen [this message]
2024-04-04 17:57 ` Bruce Jerrick
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=Zg7Ul25z75Z2YcnR@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=bmj001@gmail.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).