You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Nick Lane-Smith <ni...@apple.com> on 2004/11/05 04:44:23 UTC

[users@httpd] ServerType inetd

Hello,

In a low load environment where Apache's impact on the system needs to 
be minimized is inetd a viable option?

The blurb below doesn't mention any stability reasons for running 
apache in inetd, just that it has a high per connection cost.

What does the blurb mean by "does not always work properly"? examples?

Also inetd mode Is not recommended, is that because of the high price 
per connection or instability?

Also on a completely different track, is it possible to run apache so 
that it doesn't daemonize but still forks off children?
(e.g. sshd -D)

Thanks,
-Nick


> The ServerType directive sets how the server is executed by the 
> system. Type is one of
>
> inetd
> 		The server will be run from the system process inetd; the command to 
> start the server is added to /etc/inetd.conf
> standalone
> 		The server will run as a daemon process; the command to start the 
> server is added to the system startup scripts. (/etc/rc.local or 
> /etc/rc3.d/....)
>
> Inetd is the lesser used of the two options. For each http connection 
> received, a new copy of the server is started from scratch; after the 
> connection is complete, this program exits. There is a high price to 
> pay per connection, but for security reasons, some admins prefer this 
> option. Inetd mode is no longer recommended and does not always work 
> properly. Avoid it if at all possible.
>
> Standalone is the most common setting for ServerType since it is far 
> more efficient. The server is started once, and services all 
> subsequent connections. If you intend running Apache to serve a busy 
> site, standalone will probably be your only option.


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] ServerType inetd

Posted by Joshua Slive <js...@gmail.com>.
On Thu, 4 Nov 2004 19:44:23 -0800, Nick Lane-Smith <ni...@apple.com> wrote:
> Hello,
> 
> In a low load environment where Apache's impact on the system needs to
> be minimized is inetd a viable option?
> 
> The blurb below doesn't mention any stability reasons for running
> apache in inetd, just that it has a high per connection cost.
> 
> What does the blurb mean by "does not always work properly"? examples?
> 
> Also inetd mode Is not recommended, is that because of the high price
> per connection or instability?

No, it is because this mode is very rarely used (because of the
performance problems) and therefore is not at all well tested.  I
don't think there are any apache developers who run it under inetd,
and therefore there is a high probability of bugs sneaking in.

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org