[lkml]   [1996]   [Nov]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: total freeze - 2.0.23/2.0.24/2.0.25

On Wed, 20 Nov 1996, Paul Dunne wrote:

> Yes, it did! Why the bloody hell does that happen? I specifically
> didn't put the local network host in /etc/hosts because I'm running
> a local named for the network.

I just realized that I was stupidly saying NFS in my original message. I
meant DNS. (whoa, I guess I need more sleep, eh?) I'm not sure why it
wouldn't use your local named. check your /etc/resolv.conf setup stuff.

> Yes, I take your point; but I haven't been doing any programming.
> I had a stable kernel - 2.0.23, max. 14 days uptime before I shut it
> down - then I did several things: patched to 2.0.24 and then 2.0.25,
> added the local network, and stuck on the terminal. Hey, presto!
> Unstable machine, prone to freezing. I notice I say "crash" in my
> previous message; but what actually happens is a total freeze: no
> disk activity, dead keyboard, can't log in from the terminal or the
> network, the works. This must surely be a kernel problem?

Yeah, prolly. I was just pointing out that the terminal might not
necessarily be the cause.

Greg Alexander

 \ /
  Last update: 2005-03-22 13:38    [W:0.036 / U:0.640 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site