Bug#761880: [Pkg-sysvinit-devel] Bug#761880: sysv-rc: support init scripts in /lib/init.d (or similar)
control: tags -1 +moreinfo [2018-12-20 09:15] Ansgar Burchardt > > [2014-09-16 18:00] Ansgar Burchardt > >> The symlinks in /etc/rc?.d/* and /etc/default/* are configuration files, > >> but init script themselves are not (and if admins are supposed to modify > >> them, I would call them buggy). > > > > Your proposal contradicts Debian Policy (9.3.2): > > No, all scripts in /etc/init.d would still be treated as configuration > files. Just packages could choose to *not* do that (as is the sane > way) by shipping init scripts in a different location. Oh, complications. Here I support previous comment, complications, shadowing system for little gain. > Policy also seems to lag a decade behind reality: > [...] > > It's possible to disable services without editing /etc/init.d/*. > It's possible to do that without editing /etc/init.d/*. (/etc/default/*) There are other modifications admin may like to apply. We can't anticipate them all. eatmydata? nice? unshare? nsenter? > Allowing packages to not have init scripts as configuration files would > help dealing with outdated init scripts (from removed, but not purged > packages) which cause problems (for example when they lack LSB headers, > have outdated dependencies which cause cirular dependencies, ...). Yes, there is trade-off. But as I see it, your proposal favors solving issues of past (missing LSB headers, outdated scripts), which will be solved eventually, to flexibility of all current and future installation. In short: I value possibility to edit /etc/init.d/ scripts and do not find logic complexity of your proposal warranted.
Bug#761880: [Pkg-sysvinit-devel] Bug#761880: sysv-rc: support init scripts in /lib/init.d (or similar)
Control: reopen -1 Dmitry Bogatov writes: > control: tags -1 wontfix > > [2014-09-16 18:00] Ansgar Burchardt >> The symlinks in /etc/rc?.d/* and /etc/default/* are configuration files, >> but init script themselves are not (and if admins are supposed to modify >> them, I would call them buggy). > > Your proposal contradicts Debian Policy (9.3.2): No, all scripts in /etc/init.d would still be treated as configuration files. Just packages could choose to *not* do that (as is the sane way) by shipping init scripts in a different location. Policy also seems to lag a decade behind reality: > The /etc/init.d scripts must be treated as configuration files, either > (if they are present in the package, that is, in the .deb file) by > marking them as conffiles, or, (if they do not exist in the .deb) by > managing them correctly in the maintainer scripts (see Configuration > files). This is important since we want to give the local system > administrator the chance to adapt the scripts to the local system, > e.g., to disable a service without de-installing the package, or to It's possible to disable services without editing /etc/init.d/*. > specify some special command line options when starting a service, It's possible to do that without editing /etc/init.d/*. (/etc/default/*) Allowing packages to not have init scripts as configuration files would help dealing with outdated init scripts (from removed, but not purged packages) which cause problems (for example when they lack LSB headers, have outdated dependencies which cause cirular dependencies, ...). Ansgar
Bug#761880: [Pkg-sysvinit-devel] Bug#761880: sysv-rc: support init scripts in /lib/init.d (or similar)
tag 761880 wontfix severity 761880 wishlist thanks On Tue, 16 Sep 2014, Ansgar Burchardt wrote: Please support init scripts in /lib/init.d (or a similar location). Init scripts are not configuration and as such should not be installed into /etc (though I doubt we can drop support for that). No. We would have to support a shadow system, where anything in /etc/init.d would override the same named script in /lib/init.d, for no gain over what we currently have. And we are not breaking a 30-year old ABI _and_ adding undue complexity to sysv-rc without very strong reasons. Also, system initscripts *are* system configuration items, and are seldom modified by the local sysadmin. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761880: [Pkg-sysvinit-devel] Bug#761880: sysv-rc: support init scripts in /lib/init.d (or similar)
Henrique de Moraes Holschuh h...@debian.org writes: On Tue, 16 Sep 2014, Ansgar Burchardt wrote: Please support init scripts in /lib/init.d (or a similar location). Init scripts are not configuration and as such should not be installed into /etc (though I doubt we can drop support for that). No. We would have to support a shadow system, where anything in /etc/init.d would override the same named script in /lib/init.d, for no gain over what we currently have. And we are not breaking a 30-year old ABI _and_ adding undue complexity to sysv-rc without very strong reasons. Also, system initscripts *are* system configuration items, and are seldom modified by the local sysadmin. The symlinks in /etc/rc?.d/* and /etc/default/* are configuration files, but init script themselves are not (and if admins are supposed to modify them, I would call them buggy). Local sysadmins also seldom modify files below /usr (and not in /usr/local)... Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
