Are you running in a debugger when this happens or straight execution?
Running in a debugger combined with an inadvertant key stroke could cause
your debugger to halt and when another keystroke cause it to continue. This
will cause missed clock pulses also. Not saying this IS the problem, and is
rare to occur (unless acually stepping thru code with the debugger) but if
running in a debugger environment it is another possible reason this could
have happened.
Just pointing out another possible.
CyberLord
----- Original Message -----
From: Kaine LaZaro <demond@TOLKIEN.REALMS.ORG>
To: <CIRCLE@post.queensu.ca>
Sent: Thursday, February 25, 1999 12:27 AM
Subject: [Crash] Syslog.CRASH
>ok my syslog.crash had these messages at the bottem of the file, can
>anyone interpret them for me?
>Feb 24 23:41:38 :: nusage: 3 sockets connected, 3 sockets playing
>Feb 24 23:46:38 :: nusage: 3 sockets connected, 3 sockets playing
>Feb 24 23:51:38 :: nusage: 3 sockets connected, 3 sockets playing
>Feb 24 23:56:38 :: nusage: 3 sockets connected, 3 sockets playing
>Feb 25 22:00:04 :: SYSERR: Missed 79199 seconds worth of pulses.
>And then it crashes...
>
>James
>
>
>`Up, Down, Over, and Through, Back arround the Jokes on you!'
> -- Magic the Gathering
>
>
> +------------------------------------------------------------+
> | Ensure that you have read the CircleMUD Mailing List FAQ: |
> | http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
> +------------------------------------------------------------+
>
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST