delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/11/02/13:23:51

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 13:23:39 -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: <20051102182339.GC6869@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20051102174513 DOT GA6869 AT trixie DOT casa DOT cgf DOT cx> <SERRANOwAeRaNgEpTX5000000cf AT SERRANO DOT CAM DOT ARTIMI DOT COM>
Mime-Version: 1.0
In-Reply-To: <SERRANOwAeRaNgEpTX5000000cf@SERRANO.CAM.ARTIMI.COM>
User-Agent: Mutt/1.5.8i

On Wed, Nov 02, 2005 at 05:50:28PM -0000, Dave Korn wrote:
>Christopher Faylor wrote:
>> 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
>
>
>  Dunno, I think that cron_diagnose is probably a bit overly-specialised to be
>run along with every single cygcheck, and in the more general case, if lots of
>packages register check-callbacks with cygcheck, we're going to end up
>(implicitly) making it dependent on a whole lot of other stuff being there and
>working.

But, if cron is installed, and cron_diagnose fails because of other things not
being available that's useful information, too.  I'm not saying that cygcheck
should stop if cron_diagnose.sh doesn't run.

>  Perhaps if we added it under some kind of --run-extra-tests flag that was
>off by default?

If we have to ask people to do something extra then I don't think there's
a lot of benefit.  If we can ask them to use --run-extra-tests then we can
also ask them to just run cron_diagnose.sh.

Here's a scary one: How about a "cygcheck --report" option which queries
for a "from" email address and sends the report (as an attachment) to
the cygwin mailing list?

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 -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019