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 14:03:56 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygcheck improvements Message-ID: <20051102190356.GA11717@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: 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 06:31:46PM -0000, Dave Korn wrote: >Igor Pechtchanski wrote: > >> Fair enough. I guess what I was saying is that the addition of the two >> things I mentioned would make that part of cygcheck output all the more >> valuable. :-) > > Oh yes, totally agree! But that's a slightly longer-term project :) > >> BTW, one thing that's been suggested a while ago is to have cygcheck >> report the user mounts for "SYSTEM" -- that may prevent services from >> working properly, and is rather hard to get from the command line (without >> getting into the whole sysbash process, that is). > > While we're at it, it should check the owner/perms on all those >whichever-they-are logfiles that sometimes get owned by the user-id (as a >result of having tested starting up the daemon from the commandline) with >u+a/go-a perms causing services to fail when they later try to run as >SYSTEM.[*] How about checking owner/perms of standard utilities and directories? 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/