David Dyer-Bennet wrote:
> > 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.
Good point, wasn't thinking. I run apache, named, ftpd as daemons and
qmail under tcpserver.
Though I have recently thought of moving ftpd to tcpserver since it
isn't used as much.
Take Care,
--
Dale Miracle
System Administrator
Teoi Virtual Web Hosting
