Date: Tue, 12 Sep 95 15:55:23 BST
From: Andrew Wilson <andrew@tees.elsevier.co.uk>
Message-Id: <9509121455.AA14294@tees.elsevier.co.uk>
To: new-httpd@hyperreal.com
Subject: Re: MAXHOSTNAMELEN
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

> >In any case, the problem I saw with what Andy posted was, where the hell
> >do I get MAXHOSTNAMELEN from? It's defined three times and in very obscure
> >include files. Anyone have a Linux machine they'd give me an account on,
> >I'd go look around the sources myself then and see what the correct thing
> >to do is.
> 
> No point, that what the patches are for.  Sumbit your patch as you need it
> on your machine.  If it breaks on another system, then who ever is going 
> Linux at the time will submit a patch for your patch.  And we'll go from there.
> It will just take too long to try to find every machine's needs, especially when
> the original code will probebly work on 70% of the machines out there. 

It won't take too long, and it's my time, and I want to know, and I'm [buzzz]
if I'm gonna wait for list latency to slow up my patches any more.  So I'm
trying to work out what this patch needs to look like in the majority of cases,
which includes linux.  If the best linux is sensible and keeps its
param.h in /usr/include/sys then it's easy.  If not then it's less easy, but still
possible.

So I asked, anyone know what the *latest* version of Linux prefers as param.h,
if that's where it keeps its MAXHOSTNAMELENGTH, and what the value of 
MAXHOSTNAMELENGTH is?

...er, please ;)

Ay.

> <Aram>
> --
> Aram W. Mirzadeh, MIS Manager, Qosina Corporation
> http://www.qosina.com/~awm/, awm@qosina.com
> Apache httpd server team http://www.apache.org