[plug] strange modprobe using up cpu?

[Shayne O'Neill]

> Your error is different from Chris's
>
> The important line here is the "file-max limit 4096 reached"
>
> You need to tweak your /proc/sys/fs/file-max and inode-max values, or
> upgrade to a more modern kernel, which you are :)
>
> You have run out and as a result you are unable to fork any more processes
> - so the kernel can't run modprobe, and other processes are unable to fork
> ("Unable to load interpreter")

Yeah. I noticed that. Interesting the side effect was pretty similar.
Still dont know what was going berko and spawning all those processes
etc...

I've now done the following
2.4.18 kernel... bug disapears
ext3 -journal... less frightened of going to melbourne and having a crash
back home
iptables.... woohoo! firewalled that stupid virus pumping yhaaus machine
that was attacking me for weeks.

yourguild:~# netstat -t -c
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 yourguild.murdoch.e:ssh guild.murdoch.edu:37454
ESTABLISHED
tcp        0      0 yourguild.murdoch.e:ssh guild.murdoch.edu:37336
ESTABLISHED

The valley is now happy.

>
>  - Matt
>
> _______________________________________________
> PLUG discussion list: plug at plug.linux.org.au
> http://mail.plug.linux.org.au/cgi-bin/mailman/listinfo/plug
> Committee e-mail: committee at plug.linux.org.au
>