[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: qpopper through TCP wrappers



Actually, my reasoning against using this method
on a loaded machine is not due to any problem with tcpd,
but rather with inetd. Linking qpopper against libwrap
and using tcp wrappers that way is just fine even for
loaded machines, but inetd is just too costly in these
situations (forking a completely new process for each new
request of telnet/ftp/pop/whatever - fine for a small server,
death for heavily used machines).

Leonid Igolnik - LiM wrote:
> 
> |I have never used qpopper, and therefore do not know
> |if it has built-in support for tcp wrappers, but you
> |if performence is not that much of an issue (i.e., this
> |is not a machine servicing thousands of users per minute),
> Actually even if your machine is "servicing thousands" I still would
> suggest using tcpd for all kind of purposes - starting from auditing and
> logging. I know many machines ISP's and non that run pop service using
> tcpd.
> 
> |just stick it in inetd and launch thru tcpd.
> |
> |Aviram Jenik wrote:
> |>
> |> Hi.
> |>
> |> How can I run qpopper through tcp wrappers?
> |> Does it require a recompilation of qpopper?

[snip]

-- 
/---------------  Omer Efraim, omere@tcmail.tau.ac.il ------------------\
[   Microsoft Vaccine 2000 is configuring your immune system. This may  ]
[ take a few minutes. If your body stops responding for a long time and ]
[ there is no brain activity please die. Setup will continue after you  ]
[                            are reborn.                                ] 
\-----------------------------------------------------------------------/
 - Quoting Buzh, asr

S/MIME Cryptographic Signature