Re: tcpserver for pop3 and telnet
FYI I have a LWQ type pop3 install and have passed on the info to quite a few people, so I know it works. If anyone is looking for that kind of solution, just let me know and I will pass my information on again. Dave if you need any info on my install (doubtful) let me know as I would love the opportunity to pass knowledge back to LWQ. -- Tim - Original Message - From: "Dave Sill" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 28, 2001 8:40 AM Subject: Re: tcpserver for pop3 and telnet > Peter Cavender <[EMAIL PROTECTED]> wrote: > > >The LWQ description of setting up pop3 for qmail only > >says to put the tcpserver command in the qmail startup file. > > > >Shouldn't this "service" be supervised by svscan? > > Ideally, yes. > > >Why do the other qmail processes get this, but pop3 does not? > > Because the POP3 section of LWQ doesn't assume that everyone reading > it installed qmail using the LWQ directions--and I've been too lazy to > add a blurb with LWQ-specific POP3 installation instructions. > > >Also, I am moving towards eliminating inetd, and have set up in.telnetd to > >be run by tcpserver in a line in rc.local (RH Linux 6.2 here). In the > >inetd.conf file, it runs in.telnetd via /usr/sbin/tcpd. In the man page > >is says that tcps does some logging and other stuff, but I see no signs of > >it. When I try to use tcpserver->tcpd->in.telnetd, it doesn't > >work. Remove tcpd and all is fine. Should I be happy discarding tcpd? > > Yep. It doesn't do anything tcpserver can't do. > > >Also, since my inetd.conf file is now *empty*, can I disable it > >altogether, or or will I lose essential internal services? > > Sure, nuke it. > > -Dave >
Re: tcpserver for pop3 and telnet
Dave Sill <[EMAIL PROTECTED]> wrote: > Peter Cavender <[EMAIL PROTECTED]> wrote: > > >Also, since my inetd.conf file is now *empty*, can I disable it > >altogether, or or will I lose essential internal services? > > Sure, nuke it. Go one step further and uninstall inetd completely. I've done it on every machine I have access to, and haven't regretted it at all. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: tcpserver for pop3 and telnet
Peter Cavender <[EMAIL PROTECTED]> wrote: >The LWQ description of setting up pop3 for qmail only >says to put the tcpserver command in the qmail startup file. > >Shouldn't this "service" be supervised by svscan? Ideally, yes. >Why do the other qmail processes get this, but pop3 does not? Because the POP3 section of LWQ doesn't assume that everyone reading it installed qmail using the LWQ directions--and I've been too lazy to add a blurb with LWQ-specific POP3 installation instructions. >Also, I am moving towards eliminating inetd, and have set up in.telnetd to >be run by tcpserver in a line in rc.local (RH Linux 6.2 here). In the >inetd.conf file, it runs in.telnetd via /usr/sbin/tcpd. In the man page >is says that tcps does some logging and other stuff, but I see no signs of >it. When I try to use tcpserver->tcpd->in.telnetd, it doesn't >work. Remove tcpd and all is fine. Should I be happy discarding tcpd? Yep. It doesn't do anything tcpserver can't do. >Also, since my inetd.conf file is now *empty*, can I disable it >altogether, or or will I lose essential internal services? Sure, nuke it. -Dave
tcpserver for pop3 and telnet
The LWQ description of setting up pop3 for qmail only says to put the tcpserver command in the qmail startup file. Shouldn't this "service" be supervised by svscan? Why do the other qmail processes get this, but pop3 does not? Also, I am moving towards eliminating inetd, and have set up in.telnetd to be run by tcpserver in a line in rc.local (RH Linux 6.2 here). In the inetd.conf file, it runs in.telnetd via /usr/sbin/tcpd. In the man page is says that tcps does some logging and other stuff, but I see no signs of it. When I try to use tcpserver->tcpd->in.telnetd, it doesn't work. Remove tcpd and all is fine. Should I be happy discarding tcpd? Also, since my inetd.conf file is now *empty*, can I disable it altogether, or or will I lose essential internal services? Is there a kit for making tcpserver mimic all the inetd services? Thanks --Pete
