X-Spam-Check-By: sourceware.org Date: Thu, 5 Jan 2006 09:38:09 -0500 (EST) From: Igor Peshansky Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: services not starting with 20060104 snapshot In-Reply-To: Message-ID: References: <43BC2659.9060709@acm.org> <20060104203344.GA18306@trixie.casa.cgf.cx> <20060105010013.GB26391@trixie.casa.cgf.cx> <20060105035924.GA29865@trixie.casa.cgf.cx> <20060105042927.GA30538@trixie.casa.cgf.cx> <20060105060545.GA31370@trixie.casa.cgf.cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Thu, 5 Jan 2006, Igor Peshansky wrote: > On Thu, 5 Jan 2006, Igor Peshansky wrote: > > > On Thu, 5 Jan 2006, Christopher Faylor wrote: > > > > > >> Also, what version of XP are you running? Pro? Is it up-to-date > > > >> with all service packs and updates? > > > > > > > >I'm running XP Pro SP1, with most updates applied (except KB835409 > > > >and KB910437, which are pending). > > > > > > Maybe that is a clue, as Yitzchak suggested. I'd missed that in the > > > cygcheck output. I'm running SP2 and I believe Corinna is also. > > > > It does look like a problem with SP1 (and Karl's message supports this > > as well). Unfortunately, I'm not at liberty to install SP2 on this > > machine (due to licensing restrictions). So I'll have to dig until a > > solution is found. > > > > Interestingly enough, the ssh daemon works just fine with the 20051003 > > snapshot. I'll try to track all the changes to fhandler_console > > between then and now to see which one tickled this problem. > > > > Thanks for helping me get to the bottom of this. > > Ok, I've tracked it down to these two changes: > and > . Commenting out > the if test in the beginning of set_console_state_for_spawn() allows the > sshd server to start successfully *and* show the output of a command. > > 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! Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.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/