William A. Hoffman wrote:
I saw some mention of this problem here:
http://www.cygwin.com/ml/cygwin/2002-07/msg00147.html
Is there a fix for this that works, or will be incorporated
into a future version of cygwin? I looked in the FAQ and
saw nothing about it. I have some nightly scripts that
I saw some mention of this problem here:
http://www.cygwin.com/ml/cygwin/2002-07/msg00147.html
Is there a fix for this that works, or will be incorporated
into a future version of cygwin? I looked in the FAQ and
saw nothing about it. I have some nightly scripts that clean
some directories, and
> Chris,
>
> OK. I ran the strace test as you requested.
>
> Here's the invocation of strace I used in place of the unadorned "rm -fr
> subdir" invocation from my earlier report:
>
> % strace -d -n -S 1 -w -o rm-fr-strace-out rm -fr subdir
>
>
> I waited a few seconds then closed the sub-window.
>
Chris,
OK. I ran the strace test as you requested.
Here's the invocation of strace I used in place of the unadorned "rm -fr
subdir" invocation from my earlier report:
% strace -d -n -S 1 -w -o rm-fr-strace-out rm -fr subdir
I waited a few seconds then closed the sub-window.
A Bzip2-compress
Chris,
I'm using BASH.
I'll let you know what the strace experiment turns up when I have some time
to give that a try.
Randall
At 10:25 2002-04-06, you wrote:
> > Chris,
> >
> > OK. Here's more information. Possibly even interesting information.
>
>Another question - which shell are you usin
> Chris,
>
> OK. Here's more information. Possibly even interesting information.
>
Another question - which shell are you using? Can you reproduce the problem
using bash?
Chris
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
> Now I do this:
>
> % mkdir subdir
> % java Writer subdir/target Now is the time
>
>
> In a separate Cygwin window:
>
> % cd tstdir
> % rm -fr subdir
>
>
> And the symptom is manifest: rm sits there, churning away, awaiting its
death at the hands of a merciless signal.
What output do you get wit
Chris,
OK. Here's more information. Possibly even interesting information.
I tried this as a test:
% mkdir tstdir
% cd tstdir
% cat >tstdir &
[1]+ Stopped cat >target
% rm target
# No complaint!
% ls -l
ls: target: Permission denied
% rm target
rm: cannot remove `target': Per
> > > Greetings,
> > >
> > > I have encountered a problem in "rm" when used with the "-f" and "-r"
> > > options and a busy and hence unremovable file is encountered.
> > >
> > > When "rm -fr" encounters a busy and hence unremovable file, it goes
into an
> > > infinite loop consuming as much CPU t
Chris,
At 09:26 2002-04-06, Chris January wrote:
> > Greetings,
> >
> > I have encountered a problem in "rm" when used with the "-f" and "-r"
> > options and a busy and hence unremovable file is encountered.
> >
> > When "rm -fr" encounters a busy and hence unremovable file, it goes into an
> > i
> Greetings,
>
> I have encountered a problem in "rm" when used with the "-f" and "-r"
> options and a busy and hence unremovable file is encountered.
>
> When "rm -fr" encounters a busy and hence unremovable file, it goes into
an
> infinite loop consuming as much CPU time as it can get until it i
Greetings,
I have encountered a problem in "rm" when used with the "-f" and "-r"
options and a busy and hence unremovable file is encountered.
When "rm -fr" encounters a busy and hence unremovable file, it goes into an
infinite loop consuming as much CPU time as it can get until it is forcibly
12 matches
Mail list logo
