Bug 184452 - xend initscript doesn't print status
Summary: xend initscript doesn't print status
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 179599
TreeView+ depends on / blocked
 
Reported: 2006-03-08 21:53 UTC by Brian Brock
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-06-14 07:48:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Brian Brock 2006-03-08 21:53:16 UTC
Description of problem:
xend initscript gives nonstandard output

xen-3.0.1-3

`service xend <function>` gives no output, differing from other init scripts.

for example:

# service xend status
#
# service xend start
#

expecting output indicating success or failure

Comment 1 Daniel Veillard 2006-06-14 07:48:38 UTC
[ reclosing after data loss on bugzilla ]

Okay I tried to fix this, I commited the change in our spec file (3.0.2-7)
it builds manually but FC6 is closed so it may take a bit before reaching
Rawhide.
This seems to work here:
[root@laptop ~]# service xend status
xend is running
[root@laptop ~]# /etc/init.d/xend stop
Stopping xend:                                             [  OK  ]
[root@laptop ~]# service xend status
xend is stopped
[root@laptop ~]# /etc/init.d/xend start
Starting xend:                                             [  OK  ]
[root@laptop ~]#

Daniel



Note You need to log in before you can comment on or make changes to this bug.