Subject: Re: sigsegv
To: None <email@example.com>
From: Simon J. Gerraty <firstname.lastname@example.org>
Date: 09/11/1996 00:46:33
In lists.netbsd.current-users you write:
>First, lynx stopped working. I didn't change anything on the system, it
>just started getting sigsegv whenever it was started. I recompiled lynx
>and the problem went away.
>Has anyone else had a problem like this? I guess this could be a hardware
>problem, but how can I tell for sure?
Not quite, though my machine crashed a couple of times a few weeks ago
because my CERN httpd proxy (which had been running happily for over a
year) decided to fork itself to death. After the 2nd crash I saw what
was going on and set a ulimit on its processes, so it would fork 40
times and then say it couldn't contact the host.
I've been running without the proxy ever since - I don't have time to
debug it just now.
-r-x--x--x 3 root wheel 2591691 Aug 7 1995 /httpd/httpd_cern*
-rwxr-xr-x 2 root wheel 925668 Feb 7 1996 /netbsd*
this is generally a very stable machine and I'm not aware of any
changes that would/should have affected httpd_cern.
The only problems I have are named occasionally getting into a state
where it simply fails to resolve anything, and running out of swap.
Both problems are resolved by daily re-starting named and all the http