Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 23 Jan 2002 17:51:10 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Problem with symlink(2) (cygwin 1.3.9) Message-ID: <20020123175110.E11608@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: <3C4EB7D2 DOT 5F49D736 AT windriver DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C4EB7D2.5F49D736@windriver.com> User-Agent: Mutt/1.3.22.1i On Wed, Jan 23, 2002 at 02:17:06PM +0100, Benoit Perrin wrote: > Hello, > > I noticed a problem with the symlink(2) API, when windows shorcuts are > used to create the links. > If a directory contains a regular file or a directory (let's say > /foo/bar), when one uses the symlink(2) API to create a soft link with > the same name: > > ret = symlink("/tmp/entry", "/foo/bar"); > > the function does not return an error (ret==-1, errno==EEXIST). This is > because the node created has the real name "/foo/bar.lnk" and not > "/foo/bar". But the visual result of this problem is that doing a 'ls' > in "/foo" lists two entries with the same name, "/foo/bar". Thanks for the report. I've checked in a fix. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/