[Subject Prev][Subject Next][Thread Prev][Thread Next][Subject Index][Thread Index]

# Checkpoint Problems Continue

- Date: Sat, 26 Jul 1997 11:54:41 -0500
- From:
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=ISO-8859-1

    After continued troubleshooting, we are still having problems with our
    checkpointing NOT executing the #0:checkpoint_started and
    #0:checkpoint_finished verbs.  The verbs are +x, and they have worked in
    the past.  The verbs are very simple and do not contain errors.  The system
    IS checkpointing at the regular intervals, which is 30 minutes.  We have
    recently upgraded to the latest server, 1.8.0p6 and the problem continues.

    Any ideas?

    Jay

    ----------
    > From: Adams, Charles J (UNK-E) <charles.j.adams@lmco.com>
    > To: 'Quinn' <quinn@netsville.com>; moo-cows@the-b.org
    > Subject: RE: unforked checkpoints
    > Date: Friday, July 25, 1997 1:51 PM
    >
    > The first should be trivial.  The second you could do easily with a "go
    > away, we're checkpointing" message, but not a "please wait" message.
    > (the "go away" message would be easy with a child process and some
    > signals, but you couldn't reconnect it to the MOO's listening port)
    >
    > > -----Original Message-----
    > > Could UNFORKED_CHECKPOINTS possibly be a $server_option?  Furthermore,
    > > could we provide a message to be shown when people connect that
    > > explains
    > > why nothing is happening?  It can be disconcerting for a player to
    > > come
    > > knocking during an unforked checkpoint and get no answer.
    > >

- Prev by Subject: binary request
- Next by Subject: Re: Checkpoint Problems Continue
- Prev by thread: EduCore-BETA Released
- Next by thread: Re: Checkpoint Problems Continue
- Index(es):
  - Subject
  - Thread

Home | Subject Index | Thread Index