Re: 2 ftpds packages conflicts
Gerrit Pape <firstname.lastname@example.org> writes:
> On Mon, Nov 06, 2006 at 11:34:14PM +0100, Sz?kelyi Szabolcs wrote:
>> can anyone tell why ftpds do conflict with each other and why httpds do
> Actually the httpds should conflict too as they install listeners on
Nope, not IMHO. There are many perfectly valid reasons for running
more than one httpd on a single machine. And even if you can't see
one, why would you want to make it impossible (aka difficult)?
> E.g.: With no httpd installed, install the apache package, apache will
> listen on 0.0.0.0:80; now install the thttpd package, it'll work fine,
> but no thttpd daemon will run afterwards, because it fails to bind to
> 0.0.0.0:80, see syslog; reboot the machine, and you'll be surprised to
> see the thttpd daemon run, and not apache, because thttpd gets started
So? It's up to the adminstrator to configure the packages after
The default of 0.0.0.0:80 may work as expected in some cases, but the
package maintainer cannot guarantee this. And that has nothing to do
with other installed packages. The maintainer just can't know what
the administrator expects.
Yes, this does go for the ftpds too. I don't see any reason why
you'd want more than one, but I don't really see any reason to impose
the restriction either. If the ftpds can be configured to listen to
anything else than 0.0.0.0:21, then the administrator should be
allowed to install more than one of them.
A warning about the need for manual configuration in the case of a
port/address conflict is probably a good idea, though.
Don't you realise that Heidegger's ghost is living in your punk