X-Spam-Check-By: sourceware.org Date: Thu, 9 Mar 2006 09:10:59 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Problems after upgrading to 1.5.19-4 Message-ID: <20060309141059.GE3979@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20060309052204.3520.qmail@web30801.mail.mud.yahoo.com> <052001c6433c$95f9c270$0201a8c0@homelarrie> <1dbcac530603082227s29ed6b1ek6c37dc60643384e6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Thu, Mar 09, 2006 at 09:06:28AM -0500, Igor Peshansky wrote: >P.S. A note for the archives: now that setup has a proper mechanism to >detect failed postinstall scripts, along with scheduling replace-on-reboot >for the files in-use, we could (should) also create a batch file in >RunOnce after reboot to re-run the failed postinstall scripts... If >someone wants to tackle this before I get to it (and it'll be a while for >me), feel free. Maybe any detection of a busy file should cause setup to write a .bat file which will run all of the post install operations at system startup rather than attempting to do this right away. Of course, there could still be a chicken/egg situation with any services. cgf -- 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/