Bug 5956 - Global rc-file in wrong place.
Global rc-file in wrong place.
Product: Red Hat Powertools
Classification: Retired
Component: xmame (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Depends On:
  Show dependency treegraph
Reported: 1999-10-14 13:59 EDT by osman
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-17 00:44:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description osman 1999-10-14 13:59:25 EDT
In the version I have
the global config file is installed in the wrong place or
the compiled-in path to it is wrong.
It is installed in "/usr/lib/games/xmame/xmamerc" but it
searches it in "usr/games/lib/xmame/xmamerc" as one can tell
when running "xmame.x11 -h"
Comment 1 Tim Powers 1999-11-22 09:23:59 EST
Where are you getting xmame.x11 from? Here is a file listing from that package:

$rpm -ql xmame

Comment 2 osman 1999-11-22 15:06:59 EST
I've got the one from the powertools/6.1
The version is xmame-0.36b1.1-2.i386.rpm
I know how the file-listing of it looks...
Read the problem carefuly please!
Comment 3 Ngo Than 2000-01-14 13:13:59 EST
i have started xmame -h
and here is the outputs:


 /usr/lib/games/xmame/xmamerc   Global configuration file
 ${HOME}/.xmame/xmamerc         User global configuration file
 ${HOME}/.xmame/<game>rc     Game-dependent user configuration file

it's ok. it searchs configfile in /usr/lib/games/xmame/xmamerc!
Comment 4 osman 2000-01-17 00:44:59 EST
Sorry that I've bothered you!
Seems like I have made a mistake for the 1st-time ever, and have confused the
self build one with the one in the premade rpm...
But if you would have read it carefully you would have noticed this...
I'm speaking of "xmame.x11 -h" that one is build for X11-ONLY and that is a
different one as in your RPM...
I was using the beta6 ...
So again sorry guys...

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