Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Date:	Wed, 2 Nov 2005 12:45:13 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: cygcheck improvements
Message-ID:	<20051102174513.GA6869@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<20051102172158 DOT GA6655 AT trixie DOT casa DOT cgf DOT cx> <SERRANO080Gxw8Zw5V6000000ce AT SERRANO DOT CAM DOT ARTIMI DOT COM>
Mime-Version:	1.0
In-Reply-To:	<SERRANO080Gxw8Zw5V6000000ce@SERRANO.CAM.ARTIMI.COM>
User-Agent:	Mutt/1.5.8i

On Wed, Nov 02, 2005 at 05:37:25PM -0000, Dave Korn wrote:
>Christopher Faylor wrote:
>> Seeing Igor's analysis of corrupt /etc/services symlinks reminded me
>> that I wanted to start a discussion on cygcheck improvements.
>> 
>> Ideally, cygcheck should report on things like /etc/services being
>> wrong.
>> 
>> What other kind of common things could cygcheck be testing for?
>
>Cygwin-related entries still pending in the Replace-on-Reboot reg key
>might be informative.....

Yep.  Good idea.

Should we run cron_diagnose.sh, too?  Or, more generically, maybe we
should have some way for packages to register themselves with cygcheck
so that cygcheck would know to run them?  That might be a catch-22, though.

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/

- Raw text -