Dale Miracle <[EMAIL PROTECTED]> writes on 18 August 2000 at 17:38:45 -0400
> [EMAIL PROTECTED] wrote:
> >
> > what consequence could happen changing inetd for ucspi-tcp?
> > I have a mail-server, Sendmail 8.9.3 (by the moment), web server (APACHE)
> >
> > Thanks
>
> Nothing but good consequences, tcpserver works very well. Sendmail
> should work fine with it, though I have never personally run sendmail
> with tcpserver. Apache on the other hand I don't think will run with
> tcpserver. I would keep apache in inetd. You can run both of them at
> the same time (inetd and tcpserver) just as long as they are running the
> same service.
While you can run Apache under inetd, it's a very bad idea except for
the smallest volume web site. Better to let it run as a daemon, where
it does useful things like reusing processes (cutting down overhead).
inetd is actually a very good idea. The particular implementation
seems to have some problems; but the idea of not having to have every
low-use specialized server always running is a good one. I run Apache
and Named and Samba as daemons, qmail under tcpserver, and leave the
rest in inetd.
--
Photos: http://dd-b.lighthunters.net/ Minicon: http://www.mnstf.org/minicon
Bookworms: http://ouroboros.demesne.com/ SF: http://www.dd-b.net/dd-b
David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
