[Bug 723603] Re: vsftpd no longer supports both anonymous_enable and local_enable

[Clint Byrum]

Alain, first, thanks for responding and working with us to try and nail
down this issue.

vsftpd is run via an upstart job when you start it with 'service vsftpd
start'. This means it will be a direct child of pid 1, and not be
subject to any of the limits you may have imposed on your login shell.
I'd say that starting it manually isn't really a supported way to start
vsftpd.

Do you get the errors about pam_shells if you start with 'service vsftpd
start', or only when starting it manually?

Marking Incomplete again, pending response from Alain. My guess is that
there's no bug, just poor documentation on best practices for daemons
that are setup to be managed via upstart.

** Changed in: vsftpd (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/723603

Title:
  vsftpd no longer supports both anonymous_enable and local_enable