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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Tue, 15 Oct 2002 20:28:20 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Robert Collins cc: Max Bowsher , "David A. Cobb" , Subject: Re: Errors during setup post-install scripts In-Reply-To: <1034724782.22361.34.camel@lifelesswks> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 16 Oct 2002, Robert Collins wrote: > On Wed, 2002-10-16 at 09:11, Max Bowsher wrote: > > David A. Cobb wrote: > > > Would it be a big deal to have the various setup scripts send their > > > output to, say, /var/log/setup/SCRIPTNAME.log? > > > > Probably not, but someone has to actually do it. > > It's been discussed in the cygwin-apps list, at length. I'm looking into a simple-minded way to do this, and this raised at least one question: do we actually need the output of the post-install scripts flashing in front of our eyes? If not, I can just redirect it to a file, say, /var/log/setup.log.postinstall (there's probably no need for a separate file per script). If we actually want the console windows, it'll take some more doing, probably a separate console tee-like application. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Water molecules expand as they grow warmer" (C) Popular Science, Oct'02, p.51 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/