Re: lockups in 1.7.8p4

• Date: Tue, 26 Mar 1996 07:16:31 PST
• From:
  Ranalou <ranalou@stoopid.res.wpi.edu>
• cc: MOO-Cows.PARC@xerox.com
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-to: <199603261443.JAA12540@hunny.INS.CWRU.Edu>

On Tue, 26 Mar 1996, Seth I. Rich wrote:

> YES, I know this is a no-longer-supported version of the server, but this is
> the weirdest MOO bug(?) I've seen in eons, and I'm just curious if anyone
> else has run into it.
> 
> We've got an out-of-the-box LambdaMOO 1.7.8p4 server, with
> open_network_connection enabled, running a LambdaCore-based MOO, on an
> AIX machine (I think).  If a user types a command for which argstr has
> length greater than eighty characters, the server drops that command and
> refuses to take more input from the connection.  However, the user is
> still able to -receive- data.
> 
> Has anyone ever seen this before?

Yup, but on a smaller scale...  This happens to me, personally, when I'm 
connecting straight from a dumb-terminal to the MOO.  Since the MOO does 
no terminal emulation whatsoever, I have always just expected this, more 
or less.

--
+ That Silly Ranalou Guy, ranalou@stoopid.res.wpi.edu
+ Ranalou on CowsGoMOO, stoopid.res.wpi.edu 1234  <--- Official Blatant Plug!
+ 
+ "Do not meddle in the affairs of wizards, for you are crunchy and taste good
+ with ketchup."
+                                 --Me, as Ranalou on CowsGoMOO

• lockups in 1.7.8p4
• From: "Seth I. Rich" <sir@po.cwru.edu>

• Prev: RE: lockups in 1.7.8p4
• Next: Logging to a file, instead of to stderr
• Index: MOO-cows
• Thread: MOO-cows