The problem with the machine falling into a coma when left unattended, that I mentioned a while ago, has not gone away - I still come back to it sometimes to find that, without anyone using it, it's got itself stuck somehow - seemingly doing nothing for periods of up to hours if I am gone that long. On moving the mouse, it springs back to life. This is 9.1 on a StarMax 4000/200 clone. Course, it nukes all server activity (HTTP, FTP, SMTP).
I leave Mac TCP Watcher as the only visible app now when I go away, and it does seem to be getting CPU time, as it can register all the dead connections in the connections window. Which is odd, as nothing else seems to be working. Somehow, the machine seems to be getting into a state where, for a while, it accepts incoming HTTP connections (not sure about SMTP), and may prepare responses, but they never get sent out - when the machine reawakes, it just sends back all the responses down dead sockets. Then comes the next period, where it collects all the attempted HTTP connections, but no responses are prepared - when the machine reawakes, all the response lengths are logged as zero. Then it goes totally dead and stops accepting connections at all. AIM and ICQ, for some reason, remain unaffected, but ShadowIRC is left for dead. Maybe this is because AIM and ICQ use the interrupt-level feature (or however it works) of OT - I know AIM IMs can arrive while the CPU is totally in use by another process. While Mac TCP Watcher is seemingly getting CPU time, ShadowIRC is not, as it does not detect the dead connections, so it was obviously not active - were it on the CPU, it would time stuff off, surely. The only suggestion I received the first time was to disable automatic video power down, which I tried, and that seemed to work for a while, but the frequency of the problem now suggests that it didn't work. Any suggestions as to what on earth is going on? Is, perhaps, the system getting stuck inside a blocking OT call? Would pinching a later copy of Open Transport from 9.2.2 solve this problem? (Despite it being claimed to leak RAM) But when then does it need the mouse to move to wake it up? I do wonder if it might help to toss out the Energy Saver preferences and reboot, just in case Energy Saver is fried - anyone familiar with Energy Saver being defective in this manner? Seeing as I don't actually make use of any of its services (being a live server), then could I just disable the control panel altogether and remove it from service? (i.e. does it make use of some other resident code that will still be there if I ditch the control panel?) I am so sick and tired of this problem - I just want to get it nailed, before I nail the Mac... Cheers - Dan. ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
