Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<8C6D4989662C304087C58904BAB721A54B7358@Hermes.astrum.de>
From:	Harald Kierer <Harald DOT Kierer AT astrum DOT de>
To:	"'Kevin Layer'" <layer AT franz DOT com>,
	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	RE: sh/rm bug -- rm doesn't remove a file when run from cmd
Date:	Wed, 29 Jan 2003 17:36:29 +0100
MIME-Version:	1.0

> Found the problem: I had a file named `rm':
> 
> D:\acl62\src\cl\src>ls -l rm
> -rw-r--r--    1 layer    None            0 Jan 28 15:47 rm
> D:\acl62\src\cl\src>getfacl rm
> # file: rm
> # owner: layer
> # group: None
> user::rw-
> group::r--
> other:r--
> mask:rwx
> 
> D:\acl62\src\cl\src>
> 
> Now, it seems odd that `sh' (but not `bash' nor `sh' on Solaris) would
> try and execute this.

My guess: When you start bash your pwd gets changed. Check your last line in
/etc/profile. So your "faulty" 0-byte rm is not found.
sh doesnt change the pwd, so it uses the 0-byte rm.

Bye,
 Harry

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -