From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.clark.net ([168.143.0.10]) by hawkwind.utcs.utoronto.ca with SMTP id <24628>; Wed, 5 Mar 1997 00:55:56 -0500 Received: from explorer2.clark.net (culliton@explorer2.clark.net [168.143.0.5]) by mail.clark.net (8.8.5/8.6.5) with ESMTP id AAA15859 for ; Wed, 5 Mar 1997 00:55:39 -0500 (EST) From: Tom Culliton Received: (from culliton@localhost) by explorer2.clark.net (8.8.5/8.7.1) id AAA13494 for rc@hawkwind.utcs.toronto.edu; Wed, 5 Mar 1997 00:55:45 -0500 (EST) Date: Wed, 5 Mar 1997 00:55:45 -0500 Message-Id: <199703050555.AAA13494@explorer2.clark.net> To: rc@hawkwind.utcs.toronto.edu Subject: rc, signals, readline, and Linux 8-) 8-) 8-) Anybody who has been paying attention will know that I've been fighting a battle with the combination mentioned above. Both rc and readline like to play with signals, readline always acts like a slow system call when the signal hanlder returns, and leaves things FUBAR'ed if it doesn't. 8-) 8-) 8-) So my big **** eating grin might tell you something. 8-) Thats right, unless I've overlooked something really dumb, it's fixed!!! This fix probably applies to anyone using readline, especially on Posix type systems. Basically it entails ALWAYS treating readline as a slow system call, retrying the read on EINTR, and doing some deep secret readline magic in the rc signal catcher. I'll try to post a context diff against virgin rc-1.5betadev-1 as soon as I make a few posix-isms conditional. Tom (one very tired and happy hacker)