>I have seen the same effect several times with the gopher daemon. Never
>with the NCSA httpd. I suspected, that the gopher-daemon is the bad ting,
>but maybe the kernel could do something wrong. (Linus? Any Idea?)
>(Some timer stuff going mad? Seems to be somewhat related to networking code.)
Well, personally I think that Linux returns some unexpected error code
at some point, the http daemon can't cope with that and somehow starts
expanding some buffers beyond control.
So, the problem maybe partly due to a broken kernel and partly due to
the inability to cope with the unexpected results (if at all possible,
we should fix the kernel of course).
-- Sincerely, srb@cuci.nl Stephen R. van den Berg (AKA BuGless). You are currently aboard a fully automated plane. There is no pilot on board. Rest assured, you have nothing to worry about... worry about... worry about...