httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Holsman <>
Subject RE: [PATCH] option to remove default listener
Date Fri, 18 May 2001 20:59:07 GMT
Hi Danek.
could this be more easily achieved by putting an invalid line in the configure file

or even checking for a file's presence (ie.. the default apache install would place httpd.conf
somewhere else.. your startup would check to see if httpd.conf is in the right place)

> -----Original Message-----
> From: Danek Duvall []
> Sent: Fri, May 18, 2001 1:50 PM
> To:
> Subject: Re: [PATCH] option to remove default listener
> [Sorry for the delay, and if two messages show up; I'm not sure what
> happened to the message I sent out on Wednesday.]
> On Wed, May 16, 2001 at 05:24:32PM -0700, dean gaudet wrote:
> > what does a server do when it has no default listener?  
> i.e. what's the
> > point again?
> Without my patch, a listener is created on port 80 if none has been
> configured.  With my patch, no such listener is created, and the
> appropriate return code is set such that the main loop is 
> broken, the fact
> that there are no listeners is logged, and Apache exits cleanly.
> This latter behavior is one that I'd like to make available, 
> so that we in
> Solaris-land can configure Apache to run by default, but make 
> it up to the
> end-user to enable the web server, or some other package to install a
> listener on another port.
> > (does the child_main code even work when the listener ring 
> is empty??  i
> > swear it'll core dump, but i haven't looked.)
> Well, I get no core dump, either in the threaded or the 
> prefork MPMs, and
> it looks like child_main() isn't even hit when this 
> conditional is hit.
> Danek

View raw message