vsftpd inetd -> xinetd
comfortable Slackware-user 'turned' Gentoo, here's my story:
i've got vsftp up and running smoothly on Slackware 10.1 through inetd
when i emerged vsftpd from Gentoo it merged xinetd instead of inetd
i thought, no problem, i don't mind rewriting some config files if it keeps me up to date.
it was a bit of a downer to find out the standard vsftpd-xinetd config was not working..
however, the strangest thing happened: i can get vsftp working though my old inetd config file using the `xinetd -d -inetd_compat` switch, but when i change the xinetd config file so that it creates the exact same output when running xinetd in debugging mode, it still won't work properly. [lftp with 'debug 5' gives: **** Socket error (Connection refused)]
i can provide the xinetd.conf, xinetd.d/vsftp and inetd.conf but i think the problems lies in the fact that the different types of config files are handled differently by xinetd, beyond what is visible in the debug output even. maybe someone has shared some of my experiences?
add: perhaps i was too quick to finish this post, let me paint a more vivid picture of the problem:
the service starts, and generates the same output with the xinetd-vsftpd-config as with the inetd-config, but when i actually try to connect this line is printed in the debug window:
05/6/27@03:36:14: DEBUG: 6707 {check_pipe} Got signal 17 (Child exited)
so it's a 'Signal 17'-prob i got going, maybe that rings a bell to someone
Last edited by slackster; 06-26-2005 at 06:42 PM.
|