RE: lockups in 1.7.8p4

• Date: Tue, 26 Mar 1996 07:06:17 PST
• From:
  Ron Stanions <chaeon@roc.clawpaw.com>
• Content-Transfer-Encoding: 7bit
• Content-Type: text/plain; charset="us-ascii"

Things like this have happened to me, I'm willing to bet that your connection is
PPP or SLIP based?  Check the mtu setting on your connection (and/or mru)
and increase it to 1500.  I'm not 100% sure this is the real root of the problem 
but at least in my case it solved it.


----------
From:  Seth I. Rich[SMTP:sir@po.cwru.edu]
Sent:  Tuesday, March 26, 1996 9:44 AM
To:  MOO-Cows.PARC@xerox.com
Subject:  lockups in 1.7.8p4

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.

• Prev: lockups in 1.7.8p4
• Next: Re: lockups in 1.7.8p4
• Index: MOO-cows
• Thread: MOO-cows