[649] in SIPB-AFS-requests
the trials of rosebud's pty's
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Tue Mar 31 10:07:48 1992
Date: Tue, 31 Mar 92 10:06:48 -0500
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: sipb-afsreq@Athena.MIT.EDU, sipb@Athena.MIT.EDU
(If you never use rosebud, you don't have to read this message.)
I'm sick and tired of all of this garbage with rosebud. Once again, I
can't log into it, and I therefore can't compile a SIPB program on it.
This didn't used to happen. Nothing significant has changed in the
configuration of the machine. Therefore, the most reasonable
conclusion is that someone is doing something different than has been
done in the past, and that's causing these problems.
John Carr says that either emacs or xterm is most likely the culprit.
I suspect xterm, but I don't feel like experimenting to find out.
Until the problem is found and fixed, don't run xterm or emacs in tty
mode from rosebud. Put up an xterm window on your local machine and
connect to rosebud using rlogin, but don't use xterm.
I do not think that this is a significant restriction, especially
since I don't really understand why people would need multiple windows
on a machine which is only supposed to be a file server and build
engine. I especially don't think it's a significant restriction
compared to the fact that I can't log in at all, and others have
trouble logging in as well. And I think it's a much more reasonable
restriction than rebooting the machine once a day because all of the
ptys are hosed.
And please don't tell me to run telnet sessions to grab the bad ptys.
I had 40 of them open on my workstation today, and still couldn't
rkinit (although I did finally manage to get one rlogin working after
about twenty telnets were open).
jik
