On Thu, 30 May 2013 13:59:09 -0700, Russ Allbery <r...@debian.org> wrote: >Marc Haber <mh+debian-de...@zugschlus.de> writes: >> Russ Allbery <r...@debian.org> wrote: >>> Get rid of some of that complexity because it is pointless (you'll find >>> that much of it is working around inadequacies in sysvinit). > >> Explain. > >For example, all the PID file handling is working around the inability to >determine via better mechanisms whether or not the daemon is running. >Much of the logic for changing users can be eliminated in favor of a >declarative syntax. Various logic for determining whether the daemon is >installed can be handled via a better syntax or by having the base unit >file not be a configuration file (I prefer the upstart approach here, >personally). > >Also, determining which flags to pass to the daemon from some other >configuration file, which is a common use of /etc/default files, is a hack >to work around the fact that an init script is not really user-editable. >We therefore move the parts that we expect users to change into a >separate, simpler configuration file to avoid making them brave the >dangers of the init script and deal with lots of dpkg configuration file >prompts when we fix bugs in the init script. But with a systemd or >upstart configuration file, it becomes reasonable to have the user just >edit that file directly to pass different parameters to the daemon, since >the configuration file is already as simple, in many cases, as the >/etc/default file was.
Agreed. >>> Get rid of more of it by building a static configuration from the >>> dynamic configuration when it changes, where appropriate. > >> So you are seriously suggesting to add an inotify trigger on the conf.d >> directory instead of building the configuration right before it is >> needed? > >Could you please find a better way of asking questions than putting a >bunch of words in someone else's mouth that you clearly find absurd? I'm going to try that. >When the source of the configuration is debconf, we know exactly when it >changes and don't need anything like inotify to know when to rebuild it. Disagreed, one can change a debconf-generated file manually, thanks to the debconf-is-not-a-registry mantra and the demand that a debconfed package needs to read in its configuration before presenting the debconf questions. Greetings Marc -- -------------------------------------- !! No courtesy copies, please !! ----- Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1uin12-0001cu...@swivel.zugschlus.de
