[pkg-lighttpd] Bug#642604: Bug#642604: lighttpd always binds to IPv6 on TCP port 80

[Arno Töll]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On 30.09.2011 09:23, Adam Nielsen wrote:

> if Debian decides that all pidfiles should now go into /tmp instead, 
> all users will have to examine lighttpd.conf and merge in the change

You always need to check major upgrades for changes and
incompatibilities anyway. In particular there is no guarantee your old
configuration file will work with the new daemon version.


> I realise you don't want to keep changing things, but to be honest, if
> each change is backwards compatible then you are incrementally improving
> things, which is always good.

that's only partly true. :)
I just hate splitted configuration files personally because I prefer one
single file where I can see all things I need to know at one sight.
Sometimes it makes sense to split files, e.g. for "actual configuration"
vs "site/vhost configuration" but most of the time settings spread
randomly throughout different files are hard to read, to understand and
to configure in my opinion.

This does not mean, I won't do what you suggest but you need to convince
me, why your layout is much better than mine (well - or you convince
Olaf).

> Yes, exactly.  Ideally (perhaps except for the document-root) you should
> be able to move default.conf unchanged between Debian and other distros
> and have it just work.

I'm afraid, but we have no influence at all what other distributions
choose as configuration layout and/or which files they ship. Eventually
Suse (or whatever) still continues to ship a lighttpd.conf happily
specifying their own pidfile stuff there.

If you want to introduce such a change among all Linux distributions,
you better get upstream to split their configuration files out of the
box to make sure distributions will follow more likely.



- -- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOhYV/AAoJEMcrUe6dgPNtHXsQANBhHutWDcpzJlmTBoWeekyn
hKtBxHBPmVy1goJyIO0YpwBcSbmvLnhOPmpmPMMuWI02mTAqKNPY/xF1QSJj7FH5
+O48H2qaXV749wmb81+wUxfc8KCmraga4gmYpLTKO/n0KCTMMWcjHwzyt9HFe/ec
V7owi+DKQn6J8/BMR4+0x26qy1wd2jhaGwEe1hCOSv7KDlTqXUNAYs4Xg9v2RX8l
rJqI2SURlpSUeXRmjTv0urxeIIMCD8vjEHdDBAG+OmPuyXr64QDUiOdl3bPud8+0
K5Co+Z6XbJFzXyco0LEYKlcsLaqwWmxPi7rm+y7H0/NzGIut/DA5rL1RwGYBvq8d
hv94cdl93kQ+GhhCVBiovrEizS6vJkLKjMioxkbMSnb8bTPassvcb0XrUOXbhQUF
wKCWzTOLBF891GuU/t6QEVlCb0oET5cKcBFNWocCIDZeTtpAmvYlC35NVo4L/MyE
KuKEW6L8tW+cMF8yTQyEHPfWb1McgBPpKJGXNQMRsnagONNv/3b8W9leGvE3qI5d
fc24Hs92RVOC+5861C92riq/pg4FXQYHLSWc+D69d2CLv2/4toUajOXa8FExVtxZ
463rTNVIM0DbQ19iNMBJrf7cYDNkYnbSNtYgHYVjiiMdJ4dh+T87oP8yZCVxjwKu
2HIRQQIL3Yd/Vm7roDSP
=Csz4
-----END PGP SIGNATURE-----