Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Fri, 5 Sep 2003 11:44:31 -0400 (EDT)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Jason Tishler <jason AT tishler DOT net>
cc:	cygwin AT cygwin DOT com
Subject:	Re: latest cygcheck -c is expensive
In-Reply-To:	<20030905124047.GD1852@tishler.net>
Message-ID:	<Pine.GSO.4.56.0309051113580.26266@slinky.cs.nyu.edu>
References:	<20030905124047 DOT GD1852 AT tishler DOT net>
Importance:	Normal
MIME-Version:	1.0

On Fri, 5 Sep 2003, Jason Tishler wrote:

> Igor,
>
> Would you be willing to make the status check portion of cygcheck -c
> optional (i.e., another option)?  The latest version is very expensive:
>
>     $ # 1.5.3 on P4 2.4 GHz
>     $ time cygcheck -c >/dev/null
>
>     real    1m49.646s
>     user    0m0.010s
>     sys     0m0.020s
>
>     $ # 1.3.22 on P3 500 MHz
>     $ time cygcheck -c >/dev/null
>
>     real    0m0.042s
>     user    0m0.010s
>     sys     0m0.020s
>
> Thanks,
> Jason

Jason,

What CGF said.  I assume since cygcheck can also be used to find out the
version of one installed package at a time, it might be a good idea to add
another flag.  However, I'd suggest restructuring the flags while we're at
it, i.e., only print package info if "-c" is specified (just like registry
info is only printed if "-r" is set).  Add a "-e" option that prints
environment; "-n" that checks security stuff (runs "id", checks
/etc/passwd and /etc/group, and so on), and "-i" that checks package
integrity (only valid with "-c").  Then the "-s" flag will only print the
versions of DLLs and the programs found (and the mounts).  Problem reports
will then have to include the output of "cygcheck -scnver", but, IMO, this
is worth the fine-grained control over what's printed by cygcheck.
Opinions?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

- Raw text -