Attached is a patch that seems to work on my system,
against 2.0.48.
I am not completely clear on apache memory management,
and I think it may leak the char* device memory allocated
in the url-parsing code. I am also not sure that the url
parsing code handles all cases correctly. It
does handle
William A. Rowe, Jr. wrote:
At 12:50 AM 2/13/2004, Ben Greear wrote:
The only sane answer is to pass the ports back from a parent-process
thread that spools em up. but that won't work after the connection is
accepted unless you pass them back through a Unix domain socket to
be 'blessed' by
Ben Greear wrote:
I have need of a web-server which can bind to a particular
device, both by binding to the local IP address and
also using the setsockopt(... SO_BINDTODEVICE) call.
Would there be any chance that such a patch would
be accepted into the main tree?
sure there's a chance ;) if a
Jeff Trawick wrote:
Ben Greear wrote:
I have need of a web-server which can bind to a particular
device, both by binding to the local IP address and
also using the setsockopt(... SO_BINDTODEVICE) call.
Would there be any chance that such a patch would
be accepted into the main tree?
sure
At 12:50 AM 2/13/2004, Ben Greear wrote:
Jeff Trawick wrote:
Ben Greear wrote:
I have need of a web-server which can bind to a particular
device, both by binding to the local IP address and
also using the setsockopt(... SO_BINDTODEVICE) call.
Would there be any chance that such a patch would
be
