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
Date: Mon, 10 Oct 2005 11:12:28 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: [PATCH] Bugs in cron-config: filename case and PATH
In-Reply-To: <20051010145244.GC12938@calimero.vinschen.de>
Message-ID: <Pine.GSO.4.63.0510101058030.9685@slinky.cs.nyu.edu>
References: <Pine DOT GSO DOT 4 DOT 63 DOT 0510100943300 DOT 9685 AT slinky DOT cs DOT nyu DOT edu>  <20051010145244 DOT GC12938 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 10 Oct 2005, Corinna Vinschen wrote:

> On Oct 10 10:29, Igor Pechtchanski wrote:
> > /usr/bin/cron-config doesn't work when "case_check:strict" is in effect,
>
> http://cygwin.com/cygwin-ug-net/using-cygwinenv.html, especially the
> first few words about the check_case option.  I have no inclination at
> all to support this option any further.

Yes, yes, but until that option is completely taken out (which I will
strenuously object to, and I already stated my willingness to support at
least partial functionality there), I think it makes sense to override it.
Even if case strict case checking is eventually deprecated, it'll be a
no-op.

> > as well as not setting the PATH to include /usr/bin.  So, the cron
> > service can't find cygwin1.dll, unless $PATH in the global system
> > environment contains 'c:\cygwin\bin'.
>
> Since cygrunsrv saw the light of the world for the first time, it adds
> /bin to $PATH before calling the inferior application.  So I don't see
> how adding /usr/bin to $PATH should help finding the DLL.

I've no idea either.  However, I do know that I was getting "Cannot find
cygwin1.dll" popups before adding the option, and not getting them after.

Maybe a bug in cygrunsrv?  I'll debug this, but I still think cron-config
ought to be robust.
	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!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

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