Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 2 Nov 2005 12:45:13 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygcheck improvements Message-ID: <20051102174513.GA6869@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20051102172158.GA6655@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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/