X-Spam-Check-By: sourceware.org
Date: Thu, 5 Jan 2006 15:21:37 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Karl M <karlm30 AT hotmail DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: services not starting with 20060104 snapshot
In-Reply-To: <BAY108-F66824337AB6F827402541B52E0@phx.gbl>
Message-ID: <Pine.GSO.4.63.0601051511000.24200@slinky.cs.nyu.edu>
References: <BAY108-F66824337AB6F827402541B52E0 AT phx DOT gbl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Thu, 5 Jan 2006, Karl M wrote:

> > From: Christopher Faylor
> > Subject: Re: services not starting with 20060104 snapshot
> > Date: Thu, 5 Jan 2006 11:31:13 -0500
> >
> > On Thu, Jan 05, 2006 at 10:28:23AM -0500, Igor Peshansky wrote:
> > >On Thu, 5 Jan 2006, Christopher Faylor wrote:
> > >
> > >> On Thu, Jan 05, 2006 at 09:38:09AM -0500, Igor Peshansky wrote:
> > >> >On Thu, 5 Jan 2006, Igor Peshansky wrote:
> > >> >
> > >> >> Is real_path.iscygexec() the right test for noncygwin_process?
> > >> >> It looks reversed...
> > >> >
> > >> >And indeed it was.  Negating that test brought back the output of
> > >> >commands invoked via ssh.  I'll submit a patch to cygwin-patches
> > >> >in a bit.  Whew!
> >
> > Please give yourself a gold star for tracking this down, Igor.  Maybe
> > now I can sleep tonight.
>
> I tried the latest snapshot cygwin1-200601051745.dll.bz2 on my SP1 box
> and I still can't start services; went back to cygwin1-20060103.dll.bz2.

Karl, sorry to belabor the obvious, but have you completely killed the
service processes before updating the DLL?  For me, after every
unsuccessful service startup, there was a stale cygrunsrv process left
that could be keeping the old DLL in memory.

FWIW, I have only tested this with a self-built DLL, not the snapshot.
Will do so shortly.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"


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