X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Eric Blake <ebb9 AT byu DOT net>
Subject:  Re: find -execdir command executed in wrong directory
Date: Wed, 6 Dec 2006 04:20:46 +0000 (UTC)
Lines: 17
Message-ID:  <loom.20061206T051857-170@post.gmane.org>
References:  <4576431D DOT 7060803 AT acm DOT org>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

David Rothenberger <daveroth <at> acm.org> writes:

> 
> 
> "find -execdir" seems to be executing the command in the wrong
> directory. If the file is in /tmp/a/b/c, the command is executed with
> the current directory /tmp/a/b instead of /tmp/a/b/c. oldfind does the
> right thing.

Thanks for the report. I'm forwarding it upstream, and hopefully a patch will 
be available soon.  The bug only affects the "-execdir {} +" version (you can 
still use the less efficient "-execdir {} \;").

-- 
Eric Blake
volunteer cygwin findutils maintainer



--
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/