On Thu, Apr 7, 2011 at 8:38 PM, Arno Töll <deb...@toell.net> wrote: > 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.
This is a conf file, not a doc file. There's no need to clutter the file with options that someone might change. I know that a lot of pkgs choose to do so, but IMO a link to documentation is way better. > 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 Event-handler is right by default. > 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. It's in there already. ;) Olaf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
