From: Michal Novotny <minovotn@redhat.com>
To: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
Subject: [PATCH] Fix xencommons init script chkconfig configuration
Date: Tue, 22 Jun 2010 11:05:48 +0200 [thread overview]
Message-ID: <4C207CEC.5010806@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Hi,
this is the patch to fix the xencommons init script chkconfig
configuration since the priority was missing here and chkconfig was
complaining about invalid chkconfig script so I added both start and
stop priorities to the chkconfig line and it was working fine, the
script was successfully added to chkconfig when using `chkconfig --add
xencommons` and management using the chkconfig utility was now possible.
Tested on RHEL-5 Server with Xen-4.1-unstable installed, running on
PVops kernel 2.6.32.15 and it was working fine.
Michal
Signed-off-by: Michal Novotny <minovotn@redhat.com>
--
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat
[-- Attachment #2: xen-fix-linux-init-script.patch --]
[-- Type: text/x-patch, Size: 456 bytes --]
diff -r 72c6228b5f0f tools/hotplug/Linux/init.d/xencommons
--- a/tools/hotplug/Linux/init.d/xencommons Mon Jun 21 19:19:25 2010 +0100
+++ b/tools/hotplug/Linux/init.d/xencommons Tue Jun 22 11:01:58 2010 +0200
@@ -4,7 +4,7 @@
#
# Author: Ian Jackson <ian.jackson@eu.citrix.com>
#
-# chkconfig: 2345
+# chkconfig: 2345 70 10
# description: Starts and stops xenstored and xenconsoled
### BEGIN INIT INFO
# Provides: xenstored xenconsoled
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-06-22 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 9:05 Michal Novotny [this message]
2010-06-22 9:45 ` [PATCH] Fix xencommons init script chkconfig configuration Stefano Stabellini
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=4C207CEC.5010806@redhat.com \
--to=minovotn@redhat.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.