Bug 620150 - pki-java-tools batch files fails to start on non RedHat-based distributives
pki-java-tools batch files fails to start on non RedHat-based distributives
Status: NEW
Product: Dogtag Certificate System
Classification: Community
Component: Infrastructure (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Matthew Harmsen
Ben Levenson
:
Depends On:
Blocks: 530474
  Show dependency treegraph
 
Reported: 2010-08-01 05:31 EDT by Alexander Vershilov
Modified: 2015-01-04 19:20 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alexander Vershilov 2010-08-01 05:31:22 EDT
Description of problem:

In all bash files in pki-java tools 'uname -i' is used for testing system architecture. While on many linux system there is other behavior, for example:
------
Red Hat & Cent OS
[root@base /]# uname -i                                         
x86_64
[root@base /]# uname -m 
x86_64
------
Mandriva Linux:
# uname -i
unknown
# uname -m
x86_64
------
# uname -i
unknown
uname -m
i686
------
Gentoo
# uname -i
GenuineIntel
# uname -m
x86_64
------
FreeBSD:
# uname -i
hostname
# uname -m
i386
------

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


How reproducible:
Always

Steps to Reproduce:
1. install pki-java-tools on any debian-,mandriva-,gentoo- based distributive
2. try to use any batch file from package

  
Actual results:
Program fails because it didn't know such an architecture

Expected results:
Prorgram should start

Additional info:
Changing `uname -i` to `uname -m` will help in most cases.

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