You are viewing a plain text version of this content. The canonical link for it is here.

Posted to apache-bugdb@apache.org by dg...@hyperreal.org on 1998/02/21 12:37:03 UTC

Re: os-freebsd/1748: [error] (22)Invalid argument: getsockname in error_log

[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]


Synopsis: [error] (22)Invalid argument: getsockname  in error_log

State-Changed-From-To: open-feedback
State-Changed-By: dgaudet
State-Changed-When: Sat Feb 21 03:37:02 PST 1998
State-Changed-Why:
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.

Maybe 1.3 is tickling a kernel bug.

Dean

Re: os-freebsd/1748: [error] (22)Invalid argument: getsockname in error_log

Posted by Random Junk <js...@gamespot.com>.

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.