Tom Allison wrote:

Using the yast tool I configured an xinetd entry for pure-ftp like this:

server: /usr/sbin/tcpd server arguments: /usr/sbin/pure-ftpd -A -i ....

one - it won't connect - there's 1000+ entries of "tcpd connect from..."

two - when I restart xinetd with '-d' (debug) I get very littel after it's started...

But what I do see that's strange is this: Server = /usr/sbin/tcpd Server argv = tcpd /usr/sbin/pure-ftpd.... Only from: All sites No access: No blocked sites.

I have hosts.allow set to: ftpd: 192.168.1.0/255.255.255.0 : ALLOW and hosts.deny set to: ALL : PARANOID

I think there might more than one thing that I'm doing wrong here, but I'm assuming that xinetd can use tcpd but probably not the way I configured it. Suggestions? help?

Fine. I figured all this out but I'm still getting a problem with pure-ftp not authenticating. When I run it as a daemon it will authenticate to my username. under xinetd it won't. Can't find anything in the args to mess with this. They are both set to -lpam SuSE is really starting to piss me off with their Authentication Models. Everything I've tried to do has been generally fine until I get into Authentication and then it just sucks. I've given up trying to do anything like LDAP or SQL or anything other than the strictest of defaults. And not that won't work either. No real interesting log messages, just authentication failure. ugh!!!