<HEAD><TITLE>discuss@charon: [107] in "Coldmud discussion meeting"</TITLE>
<H1>[107] in Coldmud discussion meeting</H1></HEAD>
<A HREF="/"><IMG SRC="/i-d.gif" ALT="root"></A>
<A HREF="?107"><IMG SRC="/i-back.gif" ALT="meeting"></A>
<A HREF="/help.html"><IMG SRC="/i-help.gif" ALT="help"></A>
<A HREF="1"><IMG SRC="/i-first.gif" ALT="first"></A>
<IMG SRC="/n-fref.gif" ALT="">
<IMG SRC="/n-pref.gif" ALT="">
<A HREF="106"><IMG SRC="/i-prev.gif" ALT="previous"></A>
<A HREF="108"><IMG SRC="/i-next.gif" ALT="next"></A>
<IMG SRC="/n-nref.gif" ALT="">
<IMG SRC="/n-lref.gif" ALT="">
<A HREF="1641"><IMG SRC="/i-last.gif" ALT="last"></A>
<HR><H2>hsm</H2>
<H3>daemon@ATHENA.MIT.EDU (Fri Dec 10 07:22:59 1993
)</H3>
<PRE>
Date: Fri, 10 Dec 1993 05:13:22 -0600 (MDT)
From: Lynx &lt;BRANDON@cc.usu.edu&gt;
To: coldstuff@MIT.EDU
X-Vms-To: COLDSTUFF

Recumbent did it again, but this time I was unable to get to the machine and
kill the server.  I'm not sure if this is tied to ColdMUD or not, but I do know
i've never had problems with recumbent until I started ColdMUD on it (used to 
be my old Netrek server).  Anyhow, has anybody else run a ColdMUD for long
periods of time?

In the meantime i'll be trying to figure out why recumbent finally reset itself
at 5:00 am (locked up everything at appxmtly 3:00 am)

-Brandon

</PRE>
