Yep, your right, its most likely ignoring it. I will put the "flags = NAMEINARGS"
option
in and see what changes.
I've just moved over to redhat to run a virus scanning program all all e-mail services,
and its a lot different than the old slakeware linux which I've been running for the
last
5 years so xinetd is new to me.
Andrew
Kenneth Porter wrote:
> On Thu, 2002-05-16 at 19:36, Drew wrote:
> > Hi Kenneth,
> >
> > Well all I can say is I don't have "flags = NAMEINARGS" in my xinetd file for
>ipop3
> > and qpopper is working ok with no errors. This is what is my xinted ipop3 file.
> >
> > service pop3
> > {
> > disable = no
> > socket_type = stream
> > protocol = tcp
> > port = 110
> > wait = no
> > user = root
> > server = /usr/sbin/popper
> > server_args = qpopper -s
> > }
> >
> >
> > I have look at the other service in xinetd and they don't seem to have "flags =
> > NAMEINARGS" but they do use server_args.
>
> Strange. According to "man xinetd.conf", that should pass "qpopper" in
> argv[1] and qpopper should see that as a bad argument. However, the
> startup code may simply ignore anything without a leading "-" when not
> run in standalone mode.
>
> I just ran this:
>
> egrep "(flags|server_args)" /etc/xinetd.d/*
>
> The only service which includes the name in the args and lacks
> NAMEINARGS is linuxconf. I've never tried to use that remotely (and now
> know I need to remove it) so I've never gotten an error from trying it.
