On Sun, 16 Nov 1997, Chuck Reed wrote:
> Every time I advance someone my game crashes and I get this error in
> syslog.CRASH:
>
> Sun Nov 16 02:43:35 :: Received SIGHUP, SIGINT, or SIGTERM. Shutting down...
>
> No clue why, what, when who, how, or whatever else!
>
Every process on a *nix box has a pid (Process ID). Someone on your
server with administrative access or access to your account is killing
your process, and therefore, your MUD. Basically, someone is doing the
following: (The output is from my machine, not yours so don't think that
it's me doing it.)
------------------
pangea:~/stock/bpl12$ ps
PID TTY STAT TIME COMMAND
98 5 S 0:00 -bash
144 5 S 0:00 sh ./autorun
148 5 S 0:03 bin/circle -q 4000 <<---- HEY! There's that guy's MUD!
152 5 R 0:00 ps
pangea:~/stock/bpl12$ kill 148
-------------------
I'm sure that there are other things that will cause that error message,
but that is the only way that I have seen it come up. I would suggest
that you make sure that you have permission to run a MUD on the server
that you are using. The admin may be killing the process, only to have it
pop up again because of autorun. If he gets sick of killing the MUD, you
may end up without a shell account at all.
John Evans <evansj@hi-line.net>
May the source be with you.
+------------------------------------------------------------+
| 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/08/00 PST