From: Scott Schwartz <schwartz@groucho.cse.psu.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: signals and stuff
Date: Fri, 6 May 1994 18:09:03 -0400 [thread overview]
Message-ID: <94May6.180915edt.3009@groucho.cse.psu.edu> (raw)
A while back Byron sent me this patch for 1.5beta. I don't know if it
was sent to the list, but just in case, here it is.
------- Forwarded Message
===================================================================
RCS file: RCS/input.c,v
retrieving revision 1.4
diff -c -r1.4 input.c
*** /tmp/T0a00581 Tue Apr 5 01:12:45 1994
- --- input.c Tue Apr 5 01:11:01 1994
***************
*** 140,145 ****
- --- 140,147 ----
long /*ssize_t*/ r = rc_read(istack->fd, inbuf + 2, BUFSIZE);
sigchk();
if (r < 0) {
+ if (errno == EINTR) /* retry interrupted read */
+ continue;
uerror("read");
rc_exit(1);
}
(snarfed and pasted from one xterm to another, I don't know how many
of the blanks got hosed...)
------- End of Forwarded Message
next reply other threads:[~1994-05-06 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-05-06 22:09 Scott Schwartz [this message]
1994-05-10 17:58 Tom Culliton x2278
1994-05-10 19:53 Tom Culliton x2278
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=94May6.180915edt.3009@groucho.cse.psu.edu \
--to=schwartz@groucho.cse.psu.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).