If the whole system stops responding then you most likely have a
kernel or hardware related problem.
Try excersizing your system by running other intensive applications
such as a repeated kernel build
cd /var/tmp
tar xvf linux-2.4.19.tar.gz
cd linux
make xconfig
[save and exit]
cp .config ../linux.config
cd ..
rm -rf linux
Then run the following script
#!/bin/sh -e
a=1
while true; do
echo $a >>linux.log
tar xvf linux-2.4.19.tar.gz
cd linux
cp ../linux.config .config
make dep
make clean
make bzImage
make modules
cd ..
rm -rf linux
a=`expr $a + 1`
done
This excersizes most komponents of a Linux system fairly well with a
mix of I/O intensive, CPU intensive and balanced operations..
Also see your systems messages file if there is any hints on what is
going on in the crashes.
On Thursday 05 September 2002 12.01, FEDERAL wrote:
> Can you help me with problem I faced while running Squid.
>
> Configuration:
> Slackware Linux 2.4.5
> Squid 2.4STABLE7 (the same problem with 2.4STABLE6)
>
> Problem:
> Squid is working from 2 to 30 min then Linux dies completely (Linux
> do not die if squid is not running).
> File system is damaged after system crush.
> The same configuration with kernel 2.2.19 is working OK for months.
Received on Thu Sep 05 2002 - 12:02:58 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:10:06 MST