From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 2/2] checkquorum.wdmd: add integration script with wdmd
Date: Wed, 10 Oct 2012 08:59:54 +0200 [thread overview]
Message-ID: <50751CEA.7050906@redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F75576A7D44@lisa.maurer-it.com>
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).
Fabio
1) http://www.debian.org/doc/debian-policy/ch-opersys.html
Section 9.3.2
"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, ...."
2) http://www.thefreedictionary.com/should
should (shd)
aux.v. Past tense of shall
1. Used to express obligation or duty
....
next prev parent reply other threads:[~2012-10-10 6:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 9:36 [Cluster-devel] [PATCH 1/2] cman init: make sure we start after fence_sanlockd and warn users Fabio M. Di Nitto
2012-10-09 9:36 ` [Cluster-devel] [PATCH 2/2] checkquorum.wdmd: add integration script with wdmd Fabio M. Di Nitto
2012-10-10 4:26 ` Dietmar Maurer
2012-10-10 6:59 ` Fabio M. Di Nitto [this message]
2012-10-10 8:06 ` Dietmar Maurer
2012-10-10 8:11 ` Fabio M. Di Nitto
2012-10-10 8:15 ` Dietmar Maurer
2012-10-10 11:04 ` Heiko Nardmann
2012-10-10 11:14 ` Fabio M. Di Nitto
2012-10-10 4:33 ` Dietmar Maurer
2012-10-10 7:06 ` Fabio M. Di Nitto
2012-10-10 8:10 ` Dietmar Maurer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50751CEA.7050906@redhat.com \
--to=fdinitto@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).