On 10/10/2012 6:26 AM, Dietmar Maurer wrote:
>> +# rpm based distros
>> +[ -d /etc/sysconfig ] &&
>> + [ -f /etc/sysconfig/checkquorum ] &&
>> + . /etc/sysconfig/checkquorum
>> +# deb based distros
>> +[ ! -d /etc/sysconfig ] &&
>> + [ -f /etc/default/checkquorum ] &&
>> + . /etc/default/checkquorum
> FYI: Some RAID tool vendors delivers utilities for debian which creates directory '/etc/sysconfig'
> on debian boxes, so that test is not reliable.
This might be a controversial argument.
Debian policy (1) define the use of /etc/default as "should" (2), for
conffile such as this one. On the other side it does not explicitly
forbid the use of sysconfig.
sysconfig is not found anywhere in Debian default archive because
packages to use the formal *should* policy.
If third-party applications donīt follow Debian packaging guidelines, it
is possible that they might break other components as well.
Of course we can argue on the definition of "should" forever and ever
As upstream we follow basic guidelines, distribution packagers and
porters should (pun intended
) make sure to provide us with porting
patches (thatīs also part of the Debian Maintainer duty).
"To ease the burden on the system administrator, such configurable values
should not be placed directly in the script.
Instead, they should be placed in a file in /etc/default, ...."
aux.v. Past tense of shall
1. Used to express obligation or duty