[Dovecot] Why is direct invocation of dovecot preferred over inet inclusion?
udo.rader at bestsolution.at
Tue May 15 18:08:20 EEST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Stewart Dean wrote:
> I'm used to putting things in inetd and,
> 1) should dovecot crash, I'd think it would get restarted if it was
> invoked from inet's imap-login
> 2) it would get started well after the boot
> ...wouldn't that be preferable. Enlighten me, please
this is actually a basic unix question and is absolutely not related to
essentially inetd is "bad" because starting up and closing processes
consumes lots of resources.
If you only have to handle a very small amount of clients, inetd may be
right for you, but as soon as you have to deal with more clients, inetd
is simply bad.
and about starting ... dovecot like almost any other service can of
course also be started automatically without using inetd using the usual
init scripts (depending on the unix flavour you are using).
BestSolution.at EDV Systemhaus GmbH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the dovecot