Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<3DAC84A2.7020306@cox.net>
Date:	Tue, 15 Oct 2002 17:12:02 -0400
From:	"David A. Cobb" <superbiskit AT cox DOT net>
Organization:	CoxNet User
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021009
X-Accept-Language:	en-us, en
MIME-Version:	1.0
To:	Cygwin Discussion <cygwin AT cygwin DOT com>
Subject:	Errors during setup post-install scripts

I recently needed to do a total re-install of cygwin [ totalled one 
partition ].  Took forever to get through the download stage because I 
kept getting some network problems, but it finally got to the post-install.

During the post-install I observed several failures of the usual 
fork-resource type.  However, they fly past too quickly to capture any 
useful information.  In the postinstall directory, all the scripts seem 
to have been renamed x.sh.done; so I guess they didn't totally crash the 
setup.  But I can't determine now which ones might have had problems.

Would it be a big deal to have the various setup scripts send their 
output to, say, /var/log/setup/SCRIPTNAME.log?

-- 
David A. Cobb, Software Engineer, Public Access Advocate
"By God's Grace I am a Christian man, by my actions a great sinner." -- The Way of a Pilgrim; R. M. French, tr.
Life is too short to tolerate crappy software.
.



--
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/

- Raw text -