dovecot - May 2007 - Why is direct invocation of dovecot preferred over inet inclusion?

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

-- 
===Stewart Dean, Unix System Admin, Henderson Computer Resources 
Center of Bard College, Annandale-on-Hudson, New York  12504  
sdean at bard.edu  voice: 845-758-7475, fax: 845-758-7035

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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
dovecot.

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).

- --
Udo Rader

BestSolution.at EDV Systemhaus GmbH
http://www.bestsolution.at

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org

iD8DBQFGSczkuhFd84GLxP8RAnYfAJ0WwPCToP09K0Fd26sDRJH4WaQTNQCeIML0
NW4IJkKsPhEZF7pj1mN2Fmc=J2F4
-----END PGP SIGNATURE-----