On Sun, Aug 12, 2007 at 03:50:46PM -0600, Edward F. Brown wrote: > Running multiple vsftpd daemons isn't a problem. In fact, just putting > their *.conf files in /etc/vsftpd/ will allow the default init script to > start and stop them all (just need different listen_on port options).
I know, I just wanted to confirm that it is really not possible to let vsftpd create a pid file, which is at least inconvenient. > If you want to manage them separately, with the advantages of init > scripts, you need differently named and somewhat customized init scripts. > E.g.: instead of 'killproc $prog', use 'kill -TERM portNN_vsftpd.pid', > where the pid is derived from the process using 'portNN_vsftpd.conf'; and > use unique lockfiles for portNN_vsftpd/portMM_vsftpd, to avoid multiple > daemons on either port. I'm using own init scripts (these are cluster services and I need to do some special things anyway). The best method I can think of to find the pid is using "lsof -n -i 4 -i 6 | grep ':ftp (LISTEN)'" and then grep for a particular IP address to find a specific daemon. -- -- Jos Vos <[EMAIL PROTECTED]> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
