delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
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 |
From: | "Kenneth Chalmers" <kenneth DOT chalmers AT norscan DOT com> |
To: | <cygwin AT cygwin DOT com> |
Subject: | Problem with cp and dangling symbolic link |
Date: | Thu, 26 May 2005 15:17:09 -0500 |
MIME-Version: | 1.0 |
Message-Id: | <20050526201709.4A5B4186898@liz.norscan.com> |
I've found what looks like it might be a bug in the cygwin implementation of symbolic links. It's a pretty obscure one, but I just got bitten by it so it can happen :) Here's a breakdown: 1. Create a dangling symbolic link: ln -s filename_that_doesnt_exist test 2. Copy the link, preserving its link status: cp -d test test2 3. Try to copy the link AGAIN, even with the force flag: cp -df test test2 On a Linux box, step 3 succeeds, no problem. In cygwin, I get an error: "cp: cannot create symbolic link `test2': File exists." Not sure if it's something to worry/care about, but I just thought I'd throw it out for consideration. -Ken -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |