um... checkpointing is mostly for catching infinite loops. On a heavy use/slow
machine, saving your whole world will take a bit of time. it is set to 3
minutes so that the problem HAS to be an infinite loop, and not just some god
command that is a bit intensive.
--Angus
______________________________ Forward Header __________________________________
Subject: Re: lint, Ensure++, etc
Author: INTERNET:CIRCLE@POST.QUEENSU.CA at CSERVE
Date: 4/5/98 12:41 AM
Why is the checkpointing signal set to three minutes? I can't imagine a
machine that will not be able to return control in less than 30 seconds.. or
even 5. Any poor soul who manages to dig such a machine up could surely
change the value themselves.
How about changing the value in stock to something significantly less than 3
minutes?
Crash-loop protection would be nice too. Something like 5 reboots in 30
minutes caues .killscript to be written.
--Mallory
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST