From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22959 invoked by alias); 5 Jan 2002 21:29:14 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Received: (qmail 22926 invoked from network); 5 Jan 2002 21:29:13 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 5 Jan 2002 21:29:13 -0000 Received: from cygbert.vinschen.de (cse.cygnus.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id NAA29156 for ; Sat, 5 Jan 2002 13:29:05 -0800 (PST) Received: (from corinna@localhost) by cygbert.vinschen.de (8.11.6/8.9.3/Linux sendmail 8.9.3) id g05LT3532185 for cygwin@cygwin.com; Sat, 5 Jan 2002 22:29:03 +0100 Date: Sat, 05 Jan 2002 13:29:00 -0000 From: Corinna Vinschen To: "cygwin@cygwin.com" Subject: Re: Who is supposed to set SIGURG for OOB in rlogin/tcp/rcmd?? Message-ID: <20020105222903.T27340@cygbert.vinschen.de> Mail-Followup-To: "cygwin@cygwin.com" References: <200201032147.g03LlBd04357@mail.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200201032147.g03LlBd04357@mail.redhat.com> User-Agent: Mutt/1.3.22.1i X-SW-Source: 2002-01/txt/msg00212.txt.bz2 On Thu, Jan 03, 2002 at 02:47:17PM -0700, Mark Paulus wrote: > Hi, > > I am using rlogin to talk to a sun box, and have noticed that my rows & > columns are not being set, so I'm not getting good terminal > characteristics. After digging down into the rlogin code (and cross > comparing with some debian/linux code), it seems as though someone > is not passing the SIGURG (Urgent Out Of Band data) signal back > to rlogin, and so rlogin does not know that it needs to send the > terminal characteristics back to the remote session. > > My question is, who is supposed to be passing on the SIGUSR > signal? rlogin is setting the appropriate handler, but it is never > being called. SIGURG is sort of a problem for Cygwin due to the way Winsock handles messages. In contrast to SIGURG on U*X systems, which is sent always when OOB messages arrive, the corresponding Winsock FD_OOB message is only generated when async IO is used (as is on U*X sytems with SIGIO). Unfortunately, using async IO on sockets has some unwanted side-effects. I began to implement something appropriate but my current solution breaks ssh so that's not going to help very much. The current Cygwin doesn't handle SIGURG at all and unless I can find a practical workaround for my async IO problem or unless somebody else contributes a patch this stae will not change that quickly. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/