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 From: "Dave Korn" To: Subject: RE: cygcheck improvements Date: Wed, 2 Nov 2005 17:50:28 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20051102174513.GA6869@trixie.casa.cgf.cx> Message-ID: 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. Perhaps if we added it under some kind of --run-extra-tests flag that was off by default? Hey, I had another idea. It should definitely scan /etc/postinstall and report any scripts that failed to complete (i.e. don't end with '.done'). cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/