> I've read UCSPI-TCP is very robust and reliable system. I've
> encountered that they don't work together. Who knows how to replace
> INETD with UCSPI-TCP send me some links or something else to help me
> with this question.
Inetd is a daemon that, when told to listen to a set of ports, will
launch a set of programs in response to traffic on one of those ports.
ucspi-tcp is a daemon that, when given a single port and a single
program, will listen to that port and launch that program in response to
traffic on that port. To listen to multiple services, you must run multiple
ucspi-tcp daemons.
They can, of course, coexist. The usual case is that you must
remove the line from inetd.conf that tells inetd to listen to the smtp port
before telling ucspi to listen to the smtp port. Inetd will continue to
handle the other ports you want listened to. If you're having problems
where "they don't work together," they're probably both configured to listen
on one port, and conflicting there.
In short... you probably don't want to go through the trouble of
ripping out inetd, because many of the services it handles don't approach
the load that causes inetd problems. (Of course, you can if you want to!)
--
gowen -- Greg Owen -- [EMAIL PROTECTED]
