> >> I have got it before and took appropriate steps using the ideas > >> and tips from you guys. Now I have it again: > >> > >> Current situation on my head-less system is that I do have a > >> single SSH session up. Unfortunately it's not authenticated as > >> ROOT but as an ordinary user. > >> > >> When I try a "ls" I get : > >> > >> $ ls > >> ls: .: Too many open files in system > >> > >> Trying a su gives: > >> $ su > >> /usr/libexec/ld-elf.so.1: Cannot open "/usr/lib/libutil.so.3" > >>
I would like to add that depending on what the server is doing can determine the best way to attack your problem. I have had web servers go crazy at some point (my server has been /.'d (slashdot.com) once or twice) and pulling the network cable will allow my apache processes to time out and start dying off. After a few minutes, I can su and do a reboot (or whatever.) It doesn't quite "fix" the initial problem, but does allow me to enough CPU / resources to start the shutdown process.
Just my $.02 from experience.
Justin
_______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
