[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]

    Date: Friday, 26 February 1982, 13:43-EST
    From: David Chapman <Zvona at MIT-AI>
    In-reply-to: The message of 26 Feb 82 12:21-EST from Mike McMahon <MMcM at SCRC-TENEX>

        Date: Friday, 26 February 1982, 12:21-EST
        From: Mike McMahon <MMcM at SCRC-TENEX>
        To: RICH at MIT-AI

    	Date: 26 February 1982 10:33-EST
    	From: Charles Rich <RICH at MIT-AI>
    	I type End to send the message and get an error break because the host
    	(e.g. AI) is down.  I C-Z out of the error handler, get back to the Mail
    	buffer and Abort out of it (planning to Continue later).  When I return
    	to the toplevel of Zmail and try to do anything with the keyboard or use
    	the mouse to Continue the Who-line says "LOCK".  If I M-C-Abort out of
    	this state, I get the error handler again telling me I am trying to
    	unlock a process that I didn't lock.  I use Peek to look at the
    	situation and it seems it is the Zmail-Background-process which is
    	locked.  It looks to me like there is perhaps a missing unwind-protect
    	somewhere to clear a lock.  This state is very hard to get out of.
    	All I can do is warm-boot, which still leaves Zmail sort of confused.

        I suspect that the background process is in the error handler.  You probably
        got a notification about that.  You have to get it out of there before the
        two processes can synchronize.

    In other words, do terminal-0-s to get to the background process
    pop-up window and control-z out of that.

I only got notification after I warm booted.  In response to the
notification I then did try terminal-0-s, but it had no effect.  It
still seems that the Zmail/Zwei code should protect itself from
getting into this unsynchronized state due to an i/o error, which
is a common occurence.