Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!glacier!mips!hansen
From: hansen@mips.UUCP (Craig Hansen)
Newsgroups: net.emacs
Subject: Re: Time/Load bug in Gosling
Message-ID: <397@mips.UUCP>
Date: Thu, 13-Mar-86 14:26:36 EST
Article-I.D.: mips.397
Posted: Thu Mar 13 14:26:36 1986
Date-Received: Sat, 15-Mar-86 20:25:27 EST
References: <33800005@gypsy.UUCP>
Organization: MIPS Computer Systems, Sunnyvale, CA
Lines: 29

> We are using Gosling Emacs-#264 running on a VAX 780 with 4.2BSD.  Most of
> us who use Emacs also use the 'time.ml' package to display the system time
> and load at the bottom of the screen.
> 
> In doing this we have noted a very strange feature which is not bothersome,
> but I would like to know why it happens.  What happends is that just after the
> machine crashes or is shut down and is then brought back up, it will not
> display the time and load, but rather it will just say:
> 
> 		(time and load)

I've noticed a similar problem here, but for me it's more serious.
It appears that the sub-process facility, which uses 4.2 sockets,
does not properly initialize some aspect of the "psuedo-terminal"
used in the connection.  When this happens, time.ml never updates
the "time and load" display, but also crashes unmercifully if
you try to restart time.ml, or any other sub-process (such as
when using the "compile" or "shell" packages).  I can make the
problem go away by starting a bunch of rlogin's (!) which eventually
reach the pty which causes the problems.  I've noticed that after
doing that, compile or shell processes which are started thereafter
seem to place an extra ^M at the end of each line, indicating
some misfortune with the "nl" setting on the pty.

Sigh.  Who's got the fortitude to track this junk down anymore?

Craig Hansen
MIPS Computer Systems
...decwrl!glacier!mips