[LPMOO] checkpoint causes fatal error?

• Date: Tue, 12 Dec 1995 22:39:45 PST
• From:
  Kirrily Robert <skud@glasswings.com.au>
• Content-Length: 1583
• Content-Type: text

Ok, here are the logs:

moo.log
(excluding all the rubbish of people connecting and disconnecting)

Tue Dec 12 23:49:32 AEST 1995: RESTARTED
Dec 12 23:49:32: STARTING: Version 1.7.8 of the LambdaMOO server simulation
Dec 12 23:49:32:           (DGD version 1.0.9.23)
Dec 12 23:49:32:           (LPMOO version 1.2)
Dec 12 23:49:32:           (Using protocols defined by DGD)
Dec 12 23:49:32:           (Task timeouts measured in DGD terms)
Dec 12 23:49:32: LOADING: DGD binary state dump already loaded
Dec 12 23:49:32: VALIDATING nothing optimistically ... finished.
Dec 12 23:49:32: LOADING: using state dump, will dump new database there also
Dec 13 00:45:55: CHECKPOINTING on DGD binary state file

And now for dgd.log, in its entirety, after I tried to restart the
MOO:

Precompiled: /std/auto
Precompiled: /std/core
Precompiled: /std/string
Precompiled: /std/cache
Precompiled: /lib/driver
Precompiled: /obj/listener
Precompiled: /lib/optimizer
Precompiled: /lib/compiler
Precompiled: /std/lex
Precompiled: /lib/parser
Precompiled: /lib/unparser
Precompiled: /lib/detoken
Precompiled: /lib/dns
Precompiled: /std/data
Precompiled: /lib/global
Precompiled: /std/math
Precompiled: /lib/btable
Precompiled: /std/bfuns
Precompiled: /std/kfuns
Precompiled: /std/verb
Precompiled: /std/connection
Precompiled: /obj/telnet
Precompiled: /obj/binary
Precompiled: /obj/outbound
Precompiled: /obj/object


As you can see, no error messages or anything like that... it just
*died* ... moo.log doesn't even get updated, so it's not getting ot
the point of loading the database i guess.

Skud

• Prev: Re: [LPMOO] checkpoint caused fatal crash?
• Next: [SERVER, APROG] Re: server_options:protect_whatever
• Index: MOO-cows
• Thread: MOO-cows