From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] when do I need to start cpglockd
Date: Tue, 19 Jun 2012 09:03:19 +0200 [thread overview]
Message-ID: <4FE02437.6000902@redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F754B95DD66@lisa.maurer-it.com>
On 6/19/2012 8:54 AM, Dietmar Maurer wrote:
>>> Yes, and that script 'unconditionally' (always) starts cpglockd
>>
>> Nothing wrong with that. If you ask a daemon to start it will start :)
>
> For me this is wrong. I have to maintain a debian package, and I do not want to start
> unnecessary daemons. So I simply remove that dependency.
>
If Debian handling of daemons has changed, then the change is debian
specific, it doesn?t make it a bug for all distributions.
Last I checked if I run:
apt-get install bind9 -> bind9 will start automatically. Or for that
matter also apache2 or....
The init scripts we deliver are "as generic as possible", it doesn?t
mean that they fit everything everywhere.
And then again, expressing an order is correct. If "Required-Start"
behavior in Debian is different than in other distro (I can speak for
Fedora/RHEL here), then clearly there needs to be some distro specific
"tuning".
Fabio
next prev parent reply other threads:[~2012-06-19 7:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 15:26 [Cluster-devel] when do I need to start cpglockd Dietmar Maurer
2012-06-14 12:21 ` Ryan McCabe
2012-06-14 15:41 ` Dietmar Maurer
2012-06-14 16:06 ` Ryan McCabe
2012-06-19 3:44 ` Fabio M. Di Nitto
2012-06-19 4:23 ` Dietmar Maurer
2012-06-19 6:20 ` Fabio M. Di Nitto
2012-06-19 6:54 ` Dietmar Maurer
2012-06-19 7:03 ` Fabio M. Di Nitto [this message]
2012-06-19 7:24 ` Dietmar Maurer
2012-06-19 8:04 ` Fabio M. Di Nitto
2012-06-19 8:12 ` Dietmar Maurer
2012-06-19 8:33 ` Fabio M. Di Nitto
2012-06-19 8:36 ` 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=4FE02437.6000902@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.