# listen() probs?

Brad Roberts (braddr@puremagic.com)
Mon, 1 Jul 1996 11:13:26 PDT

- Messages sorted by:[ date ][ thread ][ subject ][ author ]

    I've had this happen to a mush I've had running on a linux 1.2.11 box.
    In those cases though the problem cleard up on its own after a while.  It
    hasn't happened in a long time, as far as I know, and I've never had it
    happen to me on more recent versions of linux (1.3.x and 2.0.0).  I
    suppose I could upgrade that 1.2.11 machine to 1.2.13 or 2.0, but its not
    mine, so I don't know if upgrading to either of those will actually solve
    the problem, but it can't hurt.. much.

    On Mon, 1 Jul 1996, Jacqueline Hamilton wrote:

    >
    > In the last 24 hours I've had a weird problem happen on both of my MOOs
    > (which are running on the same machine, a Linux 1.2.11 box).  First last
    > night, the smaller moo (frontier), stopped listening on the primary port
    > (7000).  I happened to be still logged in, just other players told me
    > that they were unable to connect, and I tested it myself - even from the
    > local machine - and couldn't connect either.  ;listeners() still showed
    > up with port 7000 still in the list, but it just wasn't answering.  I
    > was able to correct that one by doing ;unlisten(7000) then ;listen(#0,7000).
    >
    > Then today, the same thing happened to my other moo (on port 7007).  I
    > knew it was still running, and I could connect to it via the web port,
    > but not the regular login port.  I had to kill -15 the moo this time and
    > restart it to fix the problem.
    >
    > Has anyone else experienced this, or have any ideas as to why it's
    > happening, and what a fix might be?
    >
    > Thanks for any info.
    >
    > -Jackie Hamilton (kira@metronet.com)
    > http://www59.metronet.com/
    >
    >