This is the mail archive of the
mailing list for the Cygwin project.
Re: services not starting with 20060104 snapshot
On Thu, Jan 05, 2006 at 09:38:09AM -0500, Igor Peshansky wrote:
>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:
>> <http://cygwin.com/ml/cygwin-cvs/2005-q4/msg00162.html> and
>> <http://cygwin.com/ml/cygwin-cvs/2005-q4/msg00166.html>. 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
>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!
You're asking if !iscygexec is the right way to detect a "noncygwin_process".
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html