Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 17 Jan 2001 12:57:09 +0100 From: Corinna Vinschen To: cygwin Subject: Re: Cygwin commands crashes after ssh login Message-ID: <20010117125709.A32026@cobold.vinschen.de> Mail-Followup-To: cygwin References: <003c01c07fb9$9e2e84e0$360510ac AT ERDELYM> <20010116143232 DOT A30565 AT cobold DOT vinschen DOT de> <292918837 DOT 20010116200818 AT logos-m DOT ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <292918837.20010116200818@logos-m.ru>; from deo@logos-m.ru on Tue, Jan 16, 2001 at 08:08:18PM +0300 On Tue, Jan 16, 2001 at 08:08:18PM +0300, Egor Duda wrote: > Hi! > > Tuesday, 16 January, 2001 Corinna Vinschen cygwin AT cygwin DOT com wrote: > > CV> Personally I'm using tcsh and bash as login shell. I'm using W2K SP1 > CV> with Cygwin 1.1.7, sshd is started via SRVANY under my own account > CV> which has the appropriate user rights and I don't have any problems > CV> using ssh and sshd on the box. > > btw, did you notice that if you try to login to _different_ account in > this configuration, sending SIGINT by pressing Ctrl-C from client side > doesn't work? > > i've traced this situation down some time ago, and the reason appeared > to be with access rights to "sigcatch" semaphore. is there any > workaround (except starting sshd under LocalSystem)? Works for me but my account used for starting sshd is in the local admin group. Could you test this in your environment, too, and report if that solves your problem? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple