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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: cygcheck improvements
Date: Wed, 2 Nov 2005 18:31:46 -0000
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.GSO.4.63.0511021318200.21380@slinky.cs.nyu.edu>
Message-ID: <SERRANOjn04x29xDbH8000000d2@SERRANO.CAM.ARTIMI.COM>

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.[*]


    cheers,
      DaveK

[*] Heh, or was it the other way round?
-- 
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/