Steve Barnes wrote: > I'd be interested to hear thoughts on this. We have a small 1U test server with 2 entry-level SATA drives that was brought to its knees twice this week by an overzealous Java process. Load averages were up around 60+ and as a result, SSH access would timeout. I don't know if this behaviour is typical across operating systems, but it's frustrating to find yourself locked out a server just because a single process went to town on the i/o subsystem. > that privileged SSH process should be spawned on RAM disk to avoid being caught up by I/O problems. Another solution would be to have core root directory (no var/log's and similar) in RAM disk (either as cache or duplicated files) so important processes are independent from I/O problems. Or maybe having that core root tree on separate HDD and separate HDD controller. Ljubomir