"Technology Strategic Planning, Inc." wrote:
>
> OK, so both xinetd and tcpserver are running. I get the feeling that I
> should pull xinetd out of the startup scripts. How will this effect apache
> and other services (most epically bind)?
>
> I assume the two don't coexist well? (A logical push-me-pull-you?)
>
> I have two instances of tcp server, both called with the command:
> /usr/local/bin/tcpserver -H -R -v -p -x /etc/tcp.smtp.cdb -u 502 -g 501 0
> smtp /var/qmail/bin/qmail-smptd
>
> xinetd is also running (one process).
>
> The other services can go; (I'd like the ability to run a web server in a
> pinch, however, the Mac can actually take care of that on an emergency basis
> (which is all I want locally).), however I need DNS on the mail box for the
> internal (NAT) DNS configuration.
Just remove any e-mail related protocols from xinetd's conf files and send
it a reload signal (SIGUSR1 if I remember correctly from my darker
experiences with it).
--
Nick (Keith) Fish
Network Engineer
Triton Technologies, Inc.
