Date: Sun, 10 Nov 1996 05:20:29 -0500 (EST) From: Jim Riffle <rif@ns.kconline.com> To: Khetan Gajjar <khetan@iafrica.com> Cc: questions@freebsd.org, Greg Hormann <ghormann@ns.kconline.com>, msmith@atrad.adelaide.edu.au Subject: Re: Perhaps the same lock up problem Message-ID: <Pine.BSI.3.95.961110051440.18362A-100000@ns.kconline.com> In-Reply-To: <Pine.BSF.3.95.961110001901.2917E-100000@chain-work.iafrica.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 10 Nov 1996, Khetan Gajjar wrote: > I noticed that a ssh I had to another machine was responding perfectly, > but as soon as I logged out of that machine, the session did not respond > anymore (i.e. when I exited the ssh and was returned to my machine). That definatly sounds like the exact thing. Once your system would have had to return to your shell and read the disk, it would not do so. > As an aside, I discovered some things which I added/changed in my kernel > which made the machine MUCH more stable (in fact, it's been up for 2 > hours, the previous record being 3 minutes. Oh wow! Now, my problem does not occur even close to that often. Of the 2 times this has happened, it was after 11 days the first time, then 18 days the second time. > file: table is full > > I see this "file: table is full" error just now - any ideas what it means > ? That could be a definate lead to the root of our problem here. Just last night, after tring to restart my name server, I received this error message: Nov 9 03:02:40 ns named[297]: socket(SOCK_DGRAM): Too many open files - exiting I had added a few domains in there, so I assumed that I screwed something up. But, that may be somthing similar to your error there. > Oh well. Here's hoping for a soln. Looks like we may be on the right track here! Jim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.961110051440.18362A-100000>