Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 453241 - gridengine-6.1u3-7.fc9.i386 is missing some files
Summary: gridengine-6.1u3-7.fc9.i386 is missing some files
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gridengine
Version: 9
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-28 09:47 UTC by Will Partain
Modified: 2008-07-14 22:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-14 22:36:38 UTC


Attachments (Terms of Use)

Description Will Partain 2008-06-28 09:47:47 UTC
Description of problem:
gridengine-6.1u3-7.fc9.i386 is missing some files.

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


How reproducible:
Trivially

Steps to Reproduce:
1. Run: ls -ld `rpm -ql gridengine`
2. See many "No such file or directory" (sample below)
3.
  
Actual results:
ls: cannot access /usr/share/gridengine/default/common/act_qmaster: No such file or 
directory
ls: cannot access /usr/share/gridengine/default/common/bootstrap: No such file or di
rectory
ls: cannot access /usr/share/gridengine/default/common/qtask: No such file or direct
ory
ls: cannot access /usr/share/gridengine/default/common/settings.csh: No such file or
 directory
ls: cannot access /usr/share/gridengine/default/common/settings.sh: No such file or 
directory


Expected results:


Additional info:

Comment 1 Orion Poplawski 2008-07-14 22:36:38 UTC
This is expected.  The files *may* be created after install by the install_*
scripts.  This allows them to be removed if needed.


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