On 1/13/09, Dave Korn wrote:
> greenup greenup wrote:
> > On 1/13/09, Mark J. Reed wrote:
> >> On Tue, Jan 13, 2009 at 2:52 PM, greenup wrote:
> >> > your perl test was a nice try; but it also did not remove the file,
> >> > which is revealing.
> >> I should have included a return code check:
> >> perl -e 'unlink("goo/foo") or die $!'
> > I really want to know the root cause, so I'm re-upgrading my cygwin
> > dll and coreutils, seeing if the dll was hiding, or some other cause
> What AV have you got? Sometimes your AV can keep a handle open to a file
> (for scanning) for some time after you've last accessed it. If you're trying
> to delete it in that window (and this could happen every time automatically
> if
> 'rm' does a stat() to check the file exists and is readable right before
> calling unlink()), then it might fail because it's in use. Maybe your AV was
> doing that for a while and now it's stopped.... but this is pretty
> speculative.
you know, I'm up for speculation right now. Even before I got to
re-upgrade, it stopped succeeding. I'm back to rm failing, and other
than opening/closing some terminal windows, I don't think I've done
anything. In one window recently I nuked my path to only /usr/bin and
tested, just incase something else was being seen.
This machine uses Mcaffee OAS. And it appears I don't have the power
to disable it even to test. Mixed feelings about that... there are
some users that would leave it off a lot...
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
