Package: debian-policy Version: 4.4.1.2 Followup-For: Bug #948115 Hi,
> Writing the scripts > ~~~~~~~~~~~~~~~~~~~ > ... > +The ``start``, ``stop``, ``restart``, and ``force-reload`` options should > +be supported by all init scripts. Supporting ``status`` is recommended but > +not required. The ``reload`` and ``try-restart`` options are optional. I wonder if it make sense to encourage or even recommend to use the interpreter in /lib/init/init-d-script for writing init scripts. Or maybe just citing that there is an interpreter and say that it's the preferred way to create init scripts, I don't know.. Anyway the interpreter would make init scripts more declarative, consistent and easier to maintain in the long run. In the version you have proposed one will discover that there is an interpreter only by typing 'man init-d-script' as suggested in the example section. I'm not speaking at behalf of sysvinit maintainers, please here from them about this. Regards, Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) debian-policy depends on no packages. Versions of packages debian-policy recommends: ii libjs-sphinxdoc 1.8.5-4 Versions of packages debian-policy suggests: it doc-base 0.10.9 -- no debconf information
