Source: debian-policy Version: 4.5.1.0 Severity: normal Currently Policy requires that init.d scripts, and only init.d scripts, don't fail if the corresponding /etc/default is removed (section 9.3.2, second-to-last paragraph).
Personally I interpret "not fail" as "succeed to function", i.e. it has to actually start the daemon. I don't think that's a particularly sensible requirement. Policy doesn't require programs to function if their native configuration files are removed, so why should default files be any different? Furthermore, this requirement doesn't exist for systemd unit files, and there are in fact unit files in the archive that fail if the default file is removed. Also, to me removing configuration files seems like a "don't break your system" kind of action. If the system administrator does it, they get to keep the pieces and are reponsible for the fallout. The other option is that "not fail" means that the init script is allowed to not start the daemon, but it shouldn't cause any further breakage. That seems like a sensible requirement to me, but the wording could use some clarification in this case.
