On Sun, August 12, 2007 9:19 am, Jos Vos wrote: > Doesn't vsftpd create a pid file when when running standalone? > > When googling I find several references to /var/run/vsftpd.pid and > /var/run/vsftpd/vsftpd.pid, but neither of them is created (also not > when I create /var/run/vsftpd). > > In fact, I would like to have a config option to specify the pid file, > in case you want to run several daemons for different purposes (multiple > bind addresses, IPv4/IPv6 etc.). It's pretty strange that such an > important daemon does not seem to have such a config option.
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). It's controlling them separately that's a little harder, but this is also true of daemons that do create, and allow configuration of, a pidfile, like sshd for example. 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. There may well be better ways to manage this (and I'd be interested in hearing about them), but this is how I deal with separate sshd processes. -Ed _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
