Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax From: info-vax@ucbvax.ARPA Newsgroups: fa.info-vax Subject: Speaking of RMS lossage... Message-ID: <6247@ucbvax.ARPA> Date: Mon, 15-Apr-85 02:52:43 EST Article-I.D.: ucbvax.6247 Posted: Mon Apr 15 02:52:43 1985 Date-Received: Tue, 16-Apr-85 00:12:07 EST Sender: daemon@ucbvax.ARPA Organization: University of California at Berkeley Lines: 20 From: *Hobbit* The discussion about RMS's synchronous behavior reminded me of another question. It used to be, under 3.x, that if you opened a mailbox [in DCL] and read from it or wrote to it, your process would LEF until the I/O was completed [like something read the mailbox at the other end]. This would happen if you did something like issued two writes; the second one would hang until the first one was read out again, emptying the mailbox. Now, under 3.x, you could ^Y out of this condition and regain control. It was a fix from 2.x in which your process would get hopelessly hung until someone else read/wrote the mailbox. Now, under 4.0, you *again* get hung if you do this! Why did they remove this??!? Is there an easy fix I'm missing? [Don't tell me to $set control=y; I've transcended to more desperate hacks.] There are times when I mess with mailboxes a lot, and being able to punt a write was real handy. Now, I have to fire up a subprocess and kill it if it gets hung. _H* -------