You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Dean Gaudet <dg...@arctic.org> on 1998/02/27 21:30:00 UTC
Re: os-freebsd/1748: [error] (22)Invalid argument: getsockname in error_log (fwd)
The following reply was made to PR os-freebsd/1748; it has been noted by GNATS.
From: Dean Gaudet <dg...@arctic.org>
To: apbugs@apache.org
Cc: Subject: Re: os-freebsd/1748: [error] (22)Invalid argument: getsockname in error_log (fwd)
Date: Fri, 27 Feb 1998 12:26:18 -0800 (PST)
---------- Forwarded message ----------
Date: Fri, 27 Feb 1998 12:21:50 -0800 (PST)
From: Random Junk <js...@gamespot.com>
To: dgaudet@hyperreal.org
Cc: apache-bugdb@apache.org, dgaudet@apache.org
Subject: Re: os-freebsd/1748: [error] (22)Invalid argument: getsockname in error_log
dgaudet@hyperreal.org writes:
> Are you sure no getsockname errors occured with 1.2.x servers?
>
> I can't see any reason why the socket would become invalid due to
> something apache does.
it happens with 1.2.5 as well.
Jon Drukman jsd@gamespot.com
----------------------------------------------------------------
Plan: Eat right, exercise regularly, die anyway.