I'll need more details if you expect me to help resolve that crash. A
stackdump is nearly useless without compiled symbols to go along it - what
was your exact command line? What version of find?
It wasn't meant to be a bug report for find(1), just a note of why I'd
stopped investigating it.
--- Phil Edwards [EMAIL PROTECTED] ha
scritto:
Try replacing spaces ' ' with dots '.' in the
paths specified with --prunepaths.
In a regexp a dot matches any character.
I had tried that, but
--prunepaths='/cygdrive/c/System.Volume.Information'
still caused the corresponding
Please don't quote email addresses unmunged. (There's a cygwin
acronym for that, but it escapes me at the moment.)
Marco Atzeri wrote:
CYGWIN_NT-5.1 ITQMOZCAS1WS875 1.7.0s(0.166/4/2)
20070224 01:25:30 i686 Cygwin
I'm using the current stable release, 1.5.24. I've been trying to use
find(1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Phil Edwards on 3/1/2007 11:24 AM:
I'm using the current stable release, 1.5.24. I've been trying to use
find(1) directly to work out a minimally successful command line, but
so far nothing. Adding -D options results in a crash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Phil Edwards on 2/27/2007 11:50 AM:
On 2/27/07, Furash Gary [EMAIL PROTECTED] wrote:
/cygdrive/c/System\ Volume\ Information
Quotes and backslashes aren't going to solve the problem, I think. I
looked at updatedb (it's a shell
; cygwin@cygwin.com
Subject: Re: Strange message from updatedb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Phil Edwards on 2/27/2007 11:50 AM:
On 2/27/07, Furash Gary [EMAIL PROTECTED] wrote:
/cygdrive/c/System\ Volume\ Information
Quotes and backslashes aren't going to solve
Try replacing spaces ' ' with dots '.' in the paths specified with --prunepaths.
In a regexp a dot matches any character.
I had tried that, but
--prunepaths='/cygdrive/c/System.Volume.Information'
still caused the corresponding directory to be searched. I didn't have
time to look further
/cygdrive/c/System\ Volume\
Information /c/cygwin'
-Original Message-
From: Phil Edwards [mailto:[EMAIL PROTECTED]
Sent: Monday, February 26, 2007 3:36 PM
To: cygwin@cygwin.com; Furash Gary; [EMAIL PROTECTED]
Subject: Re: Strange message from updatedb
Eric Blake:
/usr/bin/find: /c
On 2/27/07, Furash Gary [EMAIL PROTECTED] wrote:
/cygdrive/c/System\ Volume\ Information
Quotes and backslashes aren't going to solve the problem, I think. I
looked at updatedb (it's a shell script), and the --prunepaths
argument is passed through a sed script which replaces spaces in order
So is there anything I can do for win cygwin?
-Original Message-
From: Phil Edwards [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 27, 2007 11:51 AM
To: Furash Gary
Cc: cygwin@cygwin.com; [EMAIL PROTECTED]
Subject: Re: Strange message from updatedb
On 2/27/07, Furash Gary [EMAIL
On Tue, 27 Feb 2007, Phil Edwards wrote:
On 2/27/07, Furash Gary [EMAIL PROTECTED] wrote:
http://cygwin.com/acronyms/#PCYMTNQREAIYR. Thanks.
/cygdrive/c/System\ Volume\ Information
Quotes and backslashes aren't going to solve the problem, I think. I
looked at updatedb (it's a shell
On 2/27/07, Igor Peshansky [EMAIL PROTECTED] wrote:
On Tue, 27 Feb 2007, Phil Edwards wrote:
Quotes and backslashes aren't going to solve the problem, I think. I
looked at updatedb (it's a shell script), and the --prunepaths
argument is passed through a sed script which replaces spaces in
Phil Edwards wrote:
I'm aware of the restrictions, and I will bet long odds that spaces
show up in filenames far more often than colons (or any other
punctuation commonly used as a separator in pathname lists) are used.
I've not changed my opinion that updatedb is behind the times and is
On Tue, Feb 27, 2007 at 04:17:54PM -0700, Cary Jamison wrote:
Phil Edwards wrote:
I'm aware of the restrictions, and I will bet long odds that spaces
show up in filenames far more often than colons (or any other
punctuation commonly used as a separator in pathname lists) are used.
I've not
Christopher Faylor wrote:
On Tue, Feb 27, 2007 at 04:17:54PM -0700, Cary Jamison wrote:
Phil Edwards wrote:
I'm aware of the restrictions, and I will bet long odds that spaces
show up in filenames far more often than colons (or any other
punctuation commonly used as a separator in pathname
Furash Gary writes:
So is there anything I can do for win cygwin?
Try replacing spaces ' ' with dots '.' in the paths specified with --prunepaths.
In a regexp a dot matches any character.
--
Enrico
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
Eric Blake:
/usr/bin/find: /c/System Volume Information: Permission denied
Not a problem - you can't find details about certain in-use system files.
I don't think that was the question. If you note at the end of his
message, he gives the command invocation, which included that string in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Furash Gary on 2/22/2007 9:00 AM:
Here's the error messages I get
/usr/bin/updatedb: line 241: /var/locatedb.n: Permission denied
Sorry for the delay; I was on vacation. I cannot reproduce this without
more details. Do you have the
I'm running it on windows with this command
updatedb --prunepaths='/cygdrive/c/windows /cygdrive/e /cygdrive/d
/cygdrive/z cygdrive/y /proc /cygdrive/c/System\ Volume\ Information
/usr /var /cygdrive/c/Documents and Settings/furashg/Local\
Settings/Temporary\ Internet\ Files'
However, when I run
Here's the error messages I get
/usr/bin/updatedb: line 241: /var/locatedb.n: Permission denied
/usr/bin/find: Filesystem loop detected; `/c/cygwin' is part of the same
filesystem loop as `/'.
/usr/bin/find: /c/Program Files/MyEclipse Enterprise Workbench 5.1.0
20 matches
Mail list logo
