Bug 167407 - xend init script doesn't work if /usr/sbin is not in the path
Summary: xend init script doesn't work if /usr/sbin is not in the path
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Rik van Riel
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-02 13:21 UTC by Albert Strasheim
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-16 18:55:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Albert Strasheim 2005-09-02 13:21:50 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Description of problem:
The xend init script doesn't work if /sbin is not in the path. This can happen if someone logs in as a normal user and then runs su and tries to start the xend service.

The init script should refer to /usr/sbin/xend with the complete path.

Version-Release number of selected component (if applicable):
xen-2-20050823

How reproducible:
Always

Steps to Reproduce:
1. su
2. /etc/init.d/xend start
3.
  

Actual Results:  xend doesn't start

Expected Results:  xend should start

Additional info:


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