Very Computer

        Steve

--

Greyhawkes *services
http://www.veryComputer.com/

I still don't know what causes it.
I am currently running it under inetd, and the problem has only surfaced once
in several weeks.

Could you also please forward me the solution /patches for this one?

bye
Rachel

--


                http://www.zeta.org.au/~grove/grove.html

In there it mentions something about this occurring when the
port simply gets overwhelmed with requests (actually it might be
a little different, the msg in the error log cited, and what
I'm experiencing is a "connect failed: conection refused" or
something like that.) at any rate, there was some talk of
increasing the size of the buffer for the queue on the port
that _should_ be a do-able kinda thing seeing as linux comes
bundled with the source. Personally, i wouldn't know where to
begin looking to do that (ask me in a week).

At any rate, has anyone running NCSA httpd linux had problems with
a URL that does _NOT_ end in a backslash gets a 404 whilst
appending it works ok??

i.e http://whatever.com/~foobar = 404 NOT FOUND
    http://whatever.com/~foobar/ = WELCOME TO THE FOOBAR HOME PAGE

P.S. I find running in inetd _helps_ but does not alleviate
the prob. The tradeoff is I can't seem to recover memory or
swap space once it's been used until I reboot.

....does any of this sound halfway coherent????

---------------------------------------------------------------------------
Mark Jeftovic                      http://www.shmooze.net/~markjr/

---------------------------------------------------------------------------
Private World Comm. * 19 Tyndall Ave #3 * Toronto, Ont. * C eh N eh D eh * M6K 2E8