aboutsummaryrefslogtreecommitdiffstats
path: root/tools/blktap2/drivers/block-ram.c
diff options
context:
space:
mode:
authorKeir Fraser <keir@xen.org>2011-03-25 09:05:49 +0000
committerKeir Fraser <keir@xen.org>2011-03-25 09:05:49 +0000
commit847693067abd74e300e71ad1ba535d470c1b3c64 (patch)
tree170d9da5b396379501277a9cae355863a304dd1f /tools/blktap2/drivers/block-ram.c
parent9239d24b4065088101eb19a840a827d24f6aa106 (diff)
downloadxen-847693067abd74e300e71ad1ba535d470c1b3c64.tar.gz
xen-847693067abd74e300e71ad1ba535d470c1b3c64.tar.bz2
xen-847693067abd74e300e71ad1ba535d470c1b3c64.zip
init.d: Fix xencommons init script chkconfig configuration
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. Signed-off-by: Michal Novotny <minovotn@redhat.com> xen-unstable changeset: 21657:e2f5e4f3481c xen-unstable date: Tue Jun 22 16:22:30 2010 +0100
Diffstat (limited to 'tools/blktap2/drivers/block-ram.c')
0 files changed, 0 insertions, 0 deletions