Date: Fri, 6 Jan 2006 00:11:22 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: services not starting with 20060104 snapshot
Message-ID: <20060106051122.GA7778@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <43BDB8B0 DOT 8070600 AT cygwin DOT com> <20060106005917 DOT GA1937 AT trixie DOT casa DOT cgf DOT cx> <43BDC7E5 DOT 1070809 AT cygwin DOT com> <20060106015259 DOT GC1937 AT trixie DOT casa DOT cgf DOT cx> <43BDCFCC DOT 2090305 AT cygwin DOT com> <20060106023407 DOT GE1937 AT trixie DOT casa DOT cgf DOT cx> <20060106025531 DOT GG1937 AT trixie DOT casa DOT cgf DOT cx> <43BDE36A DOT 9000903 AT cygwin DOT com> <43BDE61E DOT 1000103 AT cygwin DOT com> <43BDEC67 DOT 8050506 AT cygwin DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43BDEC67.8050506@cygwin.com>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Note-from-DJ: This may be spam

On Thu, Jan 05, 2006 at 11:04:55PM -0500, Larry Hall (Cygwin) wrote:
>Chris, you asleep?  Good.  No need to disturb a good night's sleep with
>some bad news.
>
>I figured out why it didn't work for me the first time and why it did
>after that.  I think I'm finally up-to-speed with what these two competing
>blocks of code do to create this issue. ;-)  For all those wondering (does
>anybody still have the strength to keep reading this thread? ;-) ), the
>first time I tried it, sshd could not interact with the desktop.  With
>Chris's patch and this switch off, I see no extra consoles and no output
>from 'ssh localhost date'.  Turning on desktop interaction for sshd and
>restarting the service, I see no extra consoles and I get output from
>'ssh localhost date'.  It's all so obvious now. ;-)
>
>So there is still a problem (but a less than appetizing workaround).

I'm still awake.  I'm trying to create a SP1 version of Win XP from an
extra copy of XP that I have sitting around.

I didn't anticipate that this would have different effects based on
whether the service was allowed to interact with the desktop or not.  I
may be able to work around that fact.

The reason for ignoring the argument in set_console_state_for_spawn is
that I think the CreateWindowStation function always has to be called
regardless of whether it's a non-cygwin process or not.

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/