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 Date: Wed, 2 Nov 2005 12:48:08 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygcheck improvements Message-ID: <20051102174808.GB6869@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20051102172158 DOT GA6655 AT trixie DOT casa DOT cgf DOT cx> <20051102174513 DOT GA6869 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051102174513.GA6869@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.8i On Wed, Nov 02, 2005 at 12:45:13PM -0500, 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. Maybe it would be nice to detect things like "ssh installed but not configured", too. 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/