Date: Wed, 2 Apr 1997 11:04:10 -0800 (PST) From: Renaud Waldura <renaud@softway.com> To: marcs@znep.com (Marc Slemko) Cc: rw@softway.com, freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Apache lingering_close error Message-ID: <199704021904.LAA28404@softway95.softway.com> In-Reply-To: <Pine.BSF.3.95.970401182910.8420D-100000@alive.znep.com> from "Marc Slemko" at Apr 1, 97 06:39:30 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Marc Slemko wrote:
>
> There is no reason to disable linging_close for FreeBSD[1]. The message
> is simply a combination between a warning and a not-yet-removed debugging
> proxy code that I haven't had time to follow, but nothing that hurts more
> than outputting that message sometimes. It should not hurt anything. We
OK. You're a little bit difficult to follow but I think I got the
main message; sounds like a complicated issue. Thanks.
I commented out the printing; error messages bug me.
*** http_main.c Wed Apr 2 10:54:35 1997
--- http_main.c.old Fri Mar 14 08:38:53 1997
***************
*** 338,348 ****
if (((shutdown(lsd, 1)) != 0) || (fcntl(lsd, F_SETFL, FNDELAY) == -1)) {
/* if it fails, no need to go through the rest of the routine */
if (errno != ENOTCONN)
- /* RW Wed Apr 2 10:52:36 PST 1997
- This error message is actually useless (from the author)
log_unixerr("shutdown", NULL, "lingering_close", r->server);
- */
- ;
bclose(r->connection->client);
kill_timeout(r);
return;
--- 338,344 ----
--
-- Renaud Waldura -- -- Softway International, Inc -- -- rw@softway.com --
-- 185 Berry Street, Suite 5514 -- -- San Francisco, CA 94107 -- -- USA --
-- Tel (415) 896-0708 -- Fax (415) 896-0709 -- http://www.softway.com/ --
--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704021904.LAA28404>