At 05:28 PM 1/23/02, Don Clouse wrote:
>Chris,
>Running RH7.2 bare, with just qpopper installed. I have no inetd.conf
>file....where does it come from? Is there something I need to do to create
>it?
You have xinetd instead of inetd. So you need a file in the /etc/xinetd.d/
directory. I guess we'll have to start including a few samples with the
next release of popper...
After you have your file in place, use '/etc/rc.d/init.d/xinetd reload' to
get xinetd to recognize the file, and use 'chkconfig --list' to ensure it's
turned on.
Here's the content of my /etc/xinetd.d/qpopper file. You'll need to adjust
for path locations and config file locations:
# default: off
# description: The POP3 service allows remote users to access their mail \
# using an POP3 client such as Netscape Communicator, mutt, \
# or fetchmail.
service pop3
{
flags = REUSE NAMEINARGS
socket_type = stream
wait = no
user = root
server = /usr/sbin/popper
server_args = popper -f /etc/qpopper.cfg -s
instances = 50
disable = no
port = 110
per_source = 10
}
service pop3s
{
flags = REUSE NAMEINARGS
socket_type = stream
wait = no
user = root
server = /usr/sbin/popper
server_args = popper -f /etc/qpopper995.cfg -s
instances = 50
disable = no
per_source = 10
}
>Confused in Tucson,
>Don
>----- Original Message -----
>From: "Christopher Crowley" <[EMAIL PROTECTED]>
>To: "Subscribers of Qpopper" <[EMAIL PROTECTED]>
>Sent: Wednesday, January 23, 2002 7:07 AM
>Subject: Re: inetd.conf configuration?
>
>
> > > pop3 stream tcp nowait root /usr/local/bin/popper4 popper4 -f
> > > /path/to/qpop.config
> > >
> > > That all has to be on one line, of course. Note also that the service
> > > name (the first thing on the line) is pop3, not qpop3.
> >
> > Sorry, I should have been clear about that. The service's name on my
>config
> > is qpop3 because I am testing it before I implement it. qpop3 is a valid
> > service in /etc/services set to port 8110.
> >
> > Hmm. I tried that previously, and I just tried it again to double check
>that
> > I didn't make a mistake. When I insert the service name --popper4-- then
>HUP
> > inetd, the server daemon does not respond:
> >
> > Connection refused
> >
> > But, when I remove that service name, it works just fine.
> >
> >
-----------------------------------------------------------------
Daniel Senie [EMAIL PROTECTED]
Amaranth Networks Inc. http://www.amaranth.com
