X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Wed, 17 Nov 2010 16:47:36 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: sshd problem with recent snapshots
Message-ID:	<20101117154736.GC11144@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4CDEA7FB DOT 6090701 AT cornell DOT edu> <20101115160956 DOT GC17405 AT calimero DOT vinschen DOT de> <4CE15D71 DOT 1040002 AT cornell DOT edu> <20101115164013 DOT GB26984 AT ednor DOT casa DOT cgf DOT cx> <20101115165334 DOT GH17405 AT calimero DOT vinschen DOT de> <4CE1972C DOT 4080809 AT cornell DOT edu> <20101116135814 DOT GC26851 AT calimero DOT vinschen DOT de> <4CE29643 DOT 2030005 AT cornell DOT edu> <20101116145906 DOT GD26851 AT calimero DOT vinschen DOT de> <4CE3ED2A DOT 9040308 AT cornell DOT edu>
MIME-Version:	1.0
In-Reply-To:	<4CE3ED2A.9040308@cornell.edu>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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 Nov 17 09:56, Ken Brown wrote:
> On 11/16/2010 9:59 AM, Corinna Vinschen wrote:
> >The failing chmod(/dev/tty1, 0622) is actually trying to change the
> >permissions on internal objects, like events, mutexes, and pipes, which
> >together constitute a tty/pty.
> 
> Here are some more data points:
> 
> 1. I have access to four computers with Cygwin installations, and I
> can reproduce the problem on all four (including the fact that the
> problem occurs with the 9-17 snapshot but not the 9-12 snapshot).
> The computers all have similar setups and all run XP SP3, so this
> may not mean much.
> 
> 2. To rule out the most common form of BLODA, I uninstalled the
> anti-virus software on one of the computers.  This made no
> difference.
> 
> 3. All four systems have two parallel Cygwin installations.  I
> removed the second installation on one of them.  This made no
> difference.
> 
> I realize that you can't debug this if you can't reproduce it.  Is
> there anything I can try?  I don't have much programming/debugging
> experience, but I'm pretty good at following directions.

Right now, I really don't know.

Hmm.  Except, maybe, since you seem to be set up to build Cygwin from
CVS, could you start building the 09-12 version from CVS and then just 
add one change from CVS at a time using

  cvs up -D 'yyyy-mm-dd HH:MM'

as filter until you encounter the problem?  An interesting situation to
test would be, if you have the state after this change:

  2010-09-12  Corinna Vinschen  <...>

    * sec_acl.cc (acl_worker): Remove.
    (acl32): Implement acl_worker functionality here.
    (lacl32): Just return -1 with errno set to ENOSYS.
    (lacl): Ditto.
    * include/cygwin/acl.h (lacl): Remove this call.

and then just add this single change from the first 2010-09-13 checkin:

    * fhandler_tty.cc (fhandler_tty_slave::init): Use tty::setpgid method.

Then, finally, add the entire 2010-09-13 checkin.  At which point
exactly does Cygwin keel over?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -