Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For some weird reason I'm having problems getting the spawn() function working in the hosts.allow file for vsftpd. The following code:
vsftpd: ALL: \
spawn (echo LAN access to %d, Source ip=%a, Sydney time `date` \
| /bin/mail -s "LAN access to %d" root@localhost) &
hangs any connecting ftp client. The email *does* get sent to root, but the ftp client session is hung and needs to be aborted. Identical code works fine for other daemons that I've tried.
In fact, the only thing that seems to work with vsftpd is the setenv() function. All I need to do is flag root with an email when someone tries to connect to vsftpd.
I can demonstrate this behavior on Fedora Core 3 and Red Hat Enterprise Linux 3.
Any ideas anyone? Or is this a known bug with tcp_wrappers/vsftpd? Of course tcp_wrappers is enabled in the vsftpd.conf file.
I've given up. There is some serious weirdness in tcp_wrappers support inside vsftpd that I don't understand.
I've disabled tcp_wrappers support, and I'm no longer running vsftpd in stand-alone mode, instead I'm running vsftpd UNDER xinetd and the above hosts.allow file syntax work great.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.