X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <4A159D26.8000806@cornell.edu> Date: Thu, 21 May 2009 14:27:50 -0400 From: Ken Brown User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: .#* lock files under X, for files I edit??? References: <23655794 DOT post AT talk DOT nabble DOT com> <4A157FF5 DOT 6030407 AT cornell DOT edu> <23656848 DOT post AT talk DOT nabble DOT com> <4A159713 DOT 50303 AT cornell DOT edu> <297343D29C14AA4D822142893ABEAEF3066E8A21 AT srv1163ex1 DOT flightsafety DOT com> In-Reply-To: <297343D29C14AA4D822142893ABEAEF3066E8A21@srv1163ex1.flightsafety.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 5/21/2009 2:16 PM, Thrall, Bryan wrote: > It's likely that those files *ARE* symlinks; under Cygwin 1.7, symlinks > are implemented as normal files Yes, that was my point. They are cygwin symlinks, but he's examining them in an environment that doesn't recognize them as such. Look at his directory listing: > -rwxrwxrwx 1 emagiro ath 104 May 21 13:57 .#singlebuildweb.pl 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/