marc <marc...@welz.org.za> wrote: > It could be that your process table is full - Run ps fax and > understand what each process does.
Now, there's a bit of a catch 22 there ... It's headless, he's not able to SSH (or Telnet) in, and needs to log in via SSH (or Telnet) to run a command to find out why he can't connect. Only thing I can think of would be to write a script run periodically to run some diagnostics and save the results in a file - and sync after doing it. That way, as long as the file system isn't corrupted, when he's restarted the system with a brutal power off there will be some information on it's previous state. Or if it's got a serial port, run a terminal login on that - leave it logged in so you already have a shell running when the problem crops up. Or even use the serial port for the console so you get any console messages on it. _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
