Re: [imp] poppassd doesn´t work..i´m desesperated

[Brent J. Nordquist]

On Mon, 17 Dec 2001, 70210@bol.com.br <70210@bol.com.br> wrote:

> Yes the mean of the \etc\xinetd.d\poppassd  is /usr/local/bin/poppassd
> poppassd because  the sintaxe to inetd.conf is
> 
> >From code source site: http://www.netwinsite.com/poppassd/#Unix_Installation
> 
> "The file '/etc/inetd.conf' will need to be updated to accept poppassd. The
> following line will need to be added.
> 
>   poppassd stream tcp nowait root /usr/local/bin/poppassd poppassd"

That's inetd.  inetd and xinetd have completely different configuration
formats.  Just because "... /usr/local/bin/poppassd poppassd" is what you
want for inetd doesn't mean that "server_args = poppassd" is what you want
for xinetd.  I think "FreeBSD user" <freebsd@XtremeDev.com> is right; look
at the error message you're getting ("invalid option: {poppassd}").

> ----- Original Message -----
> From: "FreeBSD user" <freebsd@XtremeDev.com>
> Sent: Monday, December 17, 2001 3:11 PM
> 
> > I created a file named \etc\xinetd.d\poppassd with content:
> >
> > service poppassd
> > {
> >  socket_type = stream
> >  protocol = tcp
> >  user  = root
> >  wait  = no
> >  server =/usr/sbin/poppassd
> >  server_args =poppassd
> >  disable  = no
> > }
> 
> I've never setup poppassd before, but I run xinetd here, and it seems your
> server_args line is wrong. server_args is the flags you want to run
> /usr/sbin/poppassd with. Ie., server_args = -v -d, etc. (I'm making the
> flags up here, as I don't know what flags poppassd takes.) What you have
> right now is essentially /usr/sbin/poppassd poppassd, and I doubt that's
> right.
>
> > invalid option: {poppassd}

-- 
Brent J. Nordquist <bjn@horde.org> N0BJN       / OPN: #horde
Yahoo!: Brent_Nordquist / AIM: BrentJNordquist / ICQ: 76158942