I would think you would want to run standalone for a large operation. Running through xinetd tends to slow things down, because xinitd does not load the server untill you try to connect to its port. This is ok for services that load fast, or you don't use often, but loading Apacheeor Samba this way puts an unacceptable delay for most operations. Depending on your Apache settings, and you system speed, the connection may time out before everything loads. This is why Apache normaly keeps spare servers running...On 7/7/2004 at 10:13 PM, EE ([EMAIL PROTECTED]) wrote:
E> What is xinetd?
xinetd is an enhanced version of inetd (internet daemon), which is basically a wrapper for other internet daemons. You can use xinetd to run FTP, BIND, Apache, etc.
The benefit as opposed to standalone is that since everything goes through xinetd, you can tweak it more. Xinetd allows you to customize network utilization, set priorities for certain daemons, and tons of other crap.
If you're a desktop user (or even a small server operator), its usually better to run everything in standalone. However, for larger scale stuff xinetd is invaluable to allocating resources.
I guess you could somewhat think of it as "nice" (the program) for networking, but the analogy breaks down from there :)
Xinetd is best for low-volumn, fast loading services, not high volumn services. For a high trafic web site, xinetd would actualy use more resources the runnig Apache in the stand alone mode.
One reasion for the delay is that xinetd checks /etc/hosts.allow and /etc/hosts.deny to see if the host is allowed to connect to the service, before loading the service.
Mikkel --
Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup!
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
