>
> [1]+ Killed ./autorun (wd: ~/mud)
>
> Now, it doesn't crash-save, and according to the machine's logs, the process
> was terminated internally. However, according to the prompt on my screen,
> the process is being killed externally. As you can tell, this is a serious
> problem. I can't keep the MUD running for more than half-an-hour before it
> dies.
>
> I'm just curious if anyone else has run into similar problems and could shed
> some light on the situation.
I know that back a while ago when I worked for an ISP in chicago,
I was asked to find a way to decrease the resource congestion on the shell
machine cluster - so, I wrote a program that killed any process belonging
to a 'customer' class person who wasn't logged in, and auto-idling any one
that hadn't recieved input in a bit.
(whew. runon sentances wear me out.)
Killed around 500-600 processes in any one given day. Was
specially targeted to look at irc scripts, the 'screen' program, muds, and
other user-run servers.
Usually running a server on a given machine (ie, something that
accepts external connections) means you have to pay more. I'd bet your
admin killed it, deliberately.
PjD
+------------------------------------------------------------+
| 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 : 04/11/01 PDT