httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dirk-Willem van Gulik <dirk.vangu...@jrc.it>
Subject Re: Problems with logresolve.pl
Date Mon, 09 Mar 1998 20:10:43 GMT


On Mon, 9 Mar 1998, Rob Hartill wrote:

> On Mon, 9 Mar 1998, Dean Gaudet wrote:
> 
> > It's probably got something to do with logresolve.pl not using the
> > symbolic constants for AF_UNIX and such... and just defining them on its
> > own.
> 
> You can try the following patch but I don't think it helps.
> Does Solaris allow file based sockets ?
>
The problem might run deeper (at least on Solaris 2.4) we are currently
looking into AF_UNIX kinda sockets imply NOT working on x86 versions
of 2.4 (though works fine on Sparc's). The server/client side fire
up just fine, but the client stays forever in connect. (while the
kernel sits in a pollwait). I kind of was blaming the server side,
but it is the client on which things hang. Packeges like mSQL 1 and
mSQL 2 suffer the same fate.

Dw.
 
> Index: logresolve.pl
> ===================================================================
> RCS file: /export/home/cvs//apache-1.3/src/support/logresolve.pl,v
> retrieving revision 1.1
> diff -u -r1.1 logresolve.pl
> --- logresolve.pl	1998/01/07 17:29:01	1.1
> +++ logresolve.pl	1998/03/09 19:32:31
> @@ -53,7 +53,7 @@
>  
>  # logresolve.pl
>  #
> -# v 1.0 by robh @ imdb.com
> +# v 1.1 by robh @ imdb.com
>  # 
>  # usage: logresolve.pl <infile >outfile
>  #
> @@ -79,6 +79,11 @@
>  # I haven't yet seen any noticable reduction in the percentage of IPs
>  # that fail to get resolved. Your mileage will no doubt vary. 5s is long
>  # enough to wait IMO.
> +#
> +# Known to work with FreeBSD 2.2
> +# Known to have problems with Solaris
> +
> +require 5.004;
>  
>  $|=1;
>  
> @@ -88,8 +93,8 @@
>  use strict;
>  no strict 'refs';
>  
> -use vars qw($AF_UNIX $SOCK_STREAM $PROTOCOL);
> -($AF_UNIX, $SOCK_STREAM, $PROTOCOL) = (1, 1, 0);
> +use vars qw($PROTOCOL);
> +$PROTOCOL = 0;
>  
>  my $CHILDREN = 40;
>  my $TIMEOUT  = 5;
> @@ -137,7 +142,7 @@
>  	for (my $child = 1; $child <=$CHILDREN; $child++) {
>  		$CHILDSOCK{$child}= FileHandle->new;
>  
> -		if (!socket($CHILDSOCK{$child}, $AF_UNIX, $SOCK_STREAM, $PROTOCOL)) {
> +		if (!socket($CHILDSOCK{$child}, AF_UNIX, SOCK_STREAM, $PROTOCOL)) {
>  			warn "parent socket to child failed $!";
>  		}
>  		$filename = "./.socket.$parent.$child";
> @@ -201,7 +206,7 @@
>  	$SIG{'ALRM'} = sub { die "alarmed"; };
>  
>  	 # create a socket to communicate with parent
> -	socket(INBOUND, $AF_UNIX, $SOCK_STREAM, $PROTOCOL)
> +	socket(INBOUND, AF_UNIX, SOCK_STREAM, $PROTOCOL)
>  		|| die "Error with Socket: !$\n";
>  	$filename = "./.socket.$parent.$me";
>  	bind(INBOUND, $filename) || die "Error Binding $filename: $!\n";
> 
> 
> 
> 
> 


Mime
View raw message