public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Mark Paulus" <commpg@yahoo.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Who is supposed to set SIGURG for OOB  in rlogin/tcp/rcmd??
Date: Mon, 07 Jan 2002 09:32:00 -0000	[thread overview]
Message-ID: <20020107093200.-hP3aR27GEPbpGaIxsjzG0dW-wiA7hJtVYgZnHwZEJE@z> (raw)
In-Reply-To: <20020105222903.T27340@cygbert.vinschen.de>

Would you like some help, or what kind of patch are you
looking for? 

On Sat, 5 Jan 2002 22:29:03 +0100, Corinna Vinschen wrote:

>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/




--
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/

  reply	other threads:[~2002-01-07 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200201032147.g03LlBd04357@mail.redhat.com>
2002-01-05 13:29 ` Corinna Vinschen
2002-01-07  9:32   ` Mark Paulus [this message]
     [not found]   ` <200201071733.g07HXZd19334@mail.redhat.com>
2002-01-07 12:24     ` Corinna Vinschen
2002-01-03 13:46 Mark Paulus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020107093200.-hP3aR27GEPbpGaIxsjzG0dW-wiA7hJtVYgZnHwZEJE@z \
    --to=commpg@yahoo.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).