[dovecot] Re: inetd/xinetd/tcpserver support
Charlie Brady
charlieb-dovecot at e-smith.com
Thu Mar 6 00:14:47 EET 2003
On Wed, 26 Feb 2003, Stuart Krivis wrote:
> --On Wednesday, February 26, 2003 9:58 AM +0100 Farkas Levente
> <lfarkas at bnap.hu> wrote:
>
> > I always prefer standalone daemons, and as we see the tendency is that
> > most server run as standalone (apache, vsftpd, ssh...). at the begining
> > they has (x)inetd version later remove it... IMHO ip/tcp filtering should
> > have done in a firewall or some fitering can be implemented in the
> > standalone server too.. but this is just my 2c:-)
>
> Services that get heavily used can push inetd to its limits - or beyond. :-)
So avoid inetd. tcpserver does the job very well.
> Standalone is normally better in this case, with sendmail being a common
> example.
sendmail is not such a good example to quote for anything, especially this
week.
> >> imap stream tcp nowait root /usr/sbin/tcpd
> >> /usr/local/libexec/dovecot/imap-login imaps stream tcp nowait root
> >> /usr/sbin/tcpd /usr/local/libexec/dovecot/imap-login --ssl
>
> I don't think this will work for tcpserver. :-)
No, but a run script for using tcpserver would be something like:
#! /bin/sh
exec 2>&1
exec tcpserver \
-c 100 \
-u 0 -g 0\
-l 0 \
-HDRP \
0 143 \
/usr/local/libexec/dovecot/imap-login
> One advantage to using something sitting before the daemon is that you can
> depend on the other software for certain functionality and keep the daemon
> simple.
Yep.
--
Charlie
More information about the dovecot
mailing list