From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Tim Deegan <Tim.Deegan@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] add LSB header to xen-watchdog runlevel script [and 1 more messages]
Date: Mon, 26 Jul 2010 13:05:53 +0200 [thread overview]
Message-ID: <20100726110553.GA2641@aepfle.de> (raw)
In-Reply-To: <19533.25085.23971.650621@mariner.uk.xensource.com>
On Mon, Jul 26, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [PATCH] add LSB header to xen-watchdog runlevel script [and 1 more messages]"):
> > On Mon, 2010-07-26 at 11:08 +0100, Ian Jackson wrote:
> > > I meant: adding these lines would seem to be likely to cause some
> > > systems to automatically start the watchdog when previously they would
> > > not have done so. I wanted to know whether that was a good idea.
> >
> > IMHO no -- enabling a watchdog should be an explicit admin action.
>
> So I conclude that you think the patch is wrong ?
Ian,
the patch is not wrong. If it were, the chkconfig line had to be removed
as well. Both lines just tell the tools about the ordering in the
specifieed rulevels, when the admin actually wants to have the script
enabled by calling 'chkconfig -a xen-watchdog' or 'insserv watchdog'.
Olaf
prev parent reply other threads:[~2010-07-26 11:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 12:13 [PATCH] add LSB header to xen-watchdog runlevel script Olaf Hering
2010-07-23 16:45 ` Ian Jackson
2010-07-23 17:36 ` Olaf Hering
2010-07-23 18:04 ` Ian Jackson
2010-07-23 18:43 ` Olaf Hering
2010-07-26 9:23 ` Tim Deegan
2010-07-26 10:08 ` [PATCH] add LSB header to xen-watchdog runlevel script [and 1 more messages] Ian Jackson
2010-07-26 10:16 ` Ian Campbell
2010-07-26 10:22 ` Ian Jackson
2010-07-26 10:33 ` Ian Campbell
2010-07-26 10:53 ` Ian Jackson
2010-07-26 11:05 ` Olaf Hering [this message]
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=20100726110553.GA2641@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Tim.Deegan@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.