delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
Message-Id: | <3.0.5.32.20051212232308.009ce330@incoming.verizon.net> |
X-Sender: | phumblet AT incoming DOT verizon DOT net |
Date: | Mon, 12 Dec 2005 23:23:08 -0500 |
To: | cygwin AT cygwin DOT com |
From: | "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org> |
Subject: | Re: exim 4.54-1 and broken symlinks |
In-Reply-To: | <439D7929.7080109@byu.net> |
References: | <dnjjpu$c22$1 AT sea DOT gmane DOT org> <dn99cp$6kv$1 AT sea DOT gmane DOT org> <020a01c5fc0b$9a51d060$fb0010ac AT wirelessworld DOT airvananet DOT com> <dn9uhs$ib1$1 AT sea DOT gmane DOT org> <dna00f$nk5$1 AT sea DOT gmane DOT org> <026d01c5fc3d$68641040$fb0010ac AT wirelessworld DOT airvananet DOT com> <dnjjpu$c22$1 AT sea DOT gmane DOT org> |
Mime-Version: | 1.0 |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 |
At 06:20 AM 12/12/2005 -0700, Eric Blake wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >According to Krzysztof Duleba on 12/12/2005 3:35 AM: >> >> And ln -s -f a b produces b ==> a if a.exe doesn't exist yet. > >You are correct that the behavior of cygwin ln in the presence of symlinks >has not been consistent in the past. I think the current behavior (in >5.3.0-9 or 5.93-1) is the most sane - if linking to an existing file, .exe >is appended to the link if the existing file had .exe; otherwise, nothing >is done. There is also the cygwin-specific --disable-exe-magic option to >bypass .exe magic when creating symlinks. As long as "ln -s a.exe b" produces b ==> a.exe (and not b.exe), exim is OK. >Let me know if I need to do any further looking into the behavior of ln, >or whether this particular symlink issue is taken care of by >reinstallation and/or improved exim postinstall scripts. I think we are OK. The 4.60 version of exim released today has a postinstall script that deletes any offending exim.exe symlink. Also exim-config now detects if an exim.exe symlink or file masks the exim symlink and it acts appropriately. Pierre -- 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 |