Hi!
> I must disagree. First of all, it is an accepted policy that daemons
> on Debian do start upon installation of the package.
Indeed. It's the case for Apache, too, for example.
However, upstream, can't seem to agree on the default values either.
>From the manpage from the upstream tarball:
listen
If enabled, vsftpd will run in standalone mode. This means that vsftpd
must not be run from an inetd of some kind. Instead, the vsftpd exe‐
cutable is run once directly. vsftpd itself will then take care of
listening for and handling incoming connections.
Default: NO
listen_ipv6
Like the listen parameter, except vsftpd will listen on an IPv6
socket instead of an IPv4 one. This parameter and the listen parameter
are mutually exclusive.
Default: NO
and from the sample vsftpd.conf:
# When "listen" directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
listen=YES
#
# This directive enables listening on IPv6 sockets. To listen on IPv4
and IPv6
# sockets, you must run two copies of vsftpd with two configuration files.
# Make sure, that one of the listen options is commented !!
#listen_ipv6=YES
So, while I would like to see this bug fixed and vsftpd behave
consistently with the remaining daemon packages in Debian, I
want the end result not to deviate too much from upstream.
Might be a good idea to report this issue upstream and ask them
to fix either the manpage or the configuration file so that in
the end, both files are consistent.
I don't really want to upload the package as it is currently
found on mentors.debian.net.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
