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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.0.1.1.0.20040220213404.039ca370@127.0.0.1> X-Sender: Date: Fri, 20 Feb 2004 21:37:26 -0500 To: "Steven Hartland" , From: Larry Hall Subject: Re: tar and open files In-Reply-To: <020f01c3f811$261811f0$b3db87d4@multiplay.co.uk> References: <40369C0A DOT 50934507 AT dessent DOT net> <020f01c3f811$261811f0$b3db87d4 AT multiplay DOT co DOT uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 07:25 PM 2/20/2004, Steven Hartland you wrote: >That's a cool idea but its not an install so no pending files :( > >I was toying with the idea of amending tar for cygwin so that >it could move the offending files to a specific dir or /var/tmp >by default when encountering such a file. All the times I've >tried this its still possible to move the file even though its >locked open. Delete fails otherwise --unlink would work >Actually now I just said it could alter --unlink to do a move >if the delete failed and that would also fix and would be >a neater solution. What do people think? If it's just delaying the problem, I'm not sure this really helps. What happens when you tar again? What happens to the "thing" that's locked the file? How do you get it to "update" to the new one. If this doesn't just push the puck down the ice, I think it's a great idea. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/