lockups in 1.7.8p4

• Date: Tue, 26 Mar 1996 06:43:50 PST
• From:
  "Seth I. Rich" <sir@po.cwru.edu>
• Content-Type: text/plain; charset="us-ascii"

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?

Seth / Bb
----------------------------------------------------------------------
Seth I. Rich - sir@po.cwru.edu
                                 There is nothing more precious than
Rabbits on walls, no problem.    a tear of true repentance.

• Re: lockups in 1.7.8p4
• From: Ranalou <ranalou@stoopid.res.wpi.edu>

• Prev: Re: Local MCP editing with tf
• Next: RE: lockups in 1.7.8p4
• Index: MOO-cows
• Thread: MOO-cows