try having something like SERVER="-S not.your.ip.here,21" in conf.d/pure-ftpd when you run start on it, it returns true, but actually the daemon doesn't start because it can't bind to that IP.. Reproducible: Always Steps to Reproduce: 1. 2. 3.
which version you have installed?
1.0.18-r1
I don't see the point of having something like SERVER="-S 192.168.0.1,21" in the default configuration file. Very few people actually need to listen to a specific IP. Just remove that, the server will start the way most people want it to. Or change this to SERVER="-S 21" to just have the port in case people want to bind non-standard ports.
It's not so much the port that bothers me, but that I don't want FTP running on my other NIC. I think a lot of people with more than one NIC would agree that it's important to have that kind of control. Even if it's not important to you to have that control, I think if the init script says OK, the service should actually start, otherwise it's a real pain to find out when it's too late.
Well the version in portage now will install a server that will bind to port 21, and there is info in the file telling the user how to bind to a particular port. Thanks to Eric and "Jedi"
