-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07.04.2011 19:40, Olaf van der Spek wrote: > What other settings are you thinking about?
I was thinking, about the following directives: server.bind server.port This one is essential. Not so much because of its default value (which is 0.0.0.0) which can be left as is, but because virtually everyone may want to change this. Think yourself, what's the first thing you do, after installing a new daemon which opens network connections? You open the configuration file and adapt IP (and port) to suit your needs. If that setting is present in the default configuration file, we enhance transparency and everyone knows immediately how to achieve that task. You might know, server.port /can/ be omitted if you know what you do since there are alternative ways to pass listening ports. But I vote again for transparency here. Next is to configure the web server, this is nothing we can (or should) do for users. Therefore we end up with the same thing as before: Provide a reasonable default configuration that suits best for the vast majority of users. Afterwards you might want to tweak settings to increase performance, scale the daemon to suit your needs and so on. We should give some hints there, I was thinking about those directives: server.event-handler server.max-connections server.max-fds I was about to suggest "change event-handler to sys-epoll", but then kfreebsd and hurd came into my mind. However max-connections and/or max-fds are the first issues people run into, if there are problems. So we might provide them as well, again for transparency. For better init compatibility also server.pid-file should be set and not rely on start-stop-daemon if PID file support comes for free. (Now we're really off topic) - -- with kind regards, Arno Töll GnuPG Key-ID: 0x8408D4C4 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJNngSwAAoJELBdpXvEXpo9azsP/2mxIsRqFq//XJ/mIcYq/7/d KAw6Q6zhsubB32Muvp6cidouqGI3WLz2C334mthUw1wVO/buIIVmw0NRG8NJbQio g6VoPBHEEI3AG7J7q8kiWcb6tya67wkEKUKlV37lPXtdt1qyIanvL8zuSemqVqkk ZqER102GZ4GHgTPUjAD08esTAHBEaAG2eYKjTi166n7+qRV46egIWFFuemnV1+gv VksoQh2wakRREh+ePJOf26aFFASb0rRBticNtqS0yFRs9Gu/y216A0Z14nUlS52E gaT/+0rHHWpxBiEGQI/0tL9k6tTvXck8rVW1YfTsSr4+G2zdCCc4aYUbpHx1W9n1 q71FGuL7KYesAsXFY6hej8YhMEZ3gNVHoQUEGACS9IU72UNkpHwsig9X7luZBlGg 9MSFJkoXSyztoCNnUQ4qlVmoiGgL1NFYxW7Za6vkVwl7QMYHMd925snB1Ti+0G8M vDuOiweUTqYQC25n9KDhhKy8Zli/LZ2HBdxQBokkaPDddvQGlrRT9WTi+sgUThVK fN4yzCM86cLji5qhqdTe0GaFZnMWk2G5QalLUNTCD3WDBVpOHOqJahNa53iNd1O2 ocjYauplzRILCVBU2iTyT7ciQiIXymw0eZ2F7jXMwfcRQa7mGrfZAm+xtI2tmrCr yziRXy1cYx+v7MgwQW89 =bpVg -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
