Bug 182611 - Setup calculates required diskspace incorrectly on 64-bit machines
Setup calculates required diskspace incorrectly on 64-bit machines
Status: CLOSED CURRENTRELEASE
Product: 389
Classification: Community
Component: Install/Uninstall (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nathan Kinder
Viktor Ashirov
1.0.2
: VerifiedUpstream
Depends On:
Blocks: 183369
  Show dependency treegraph
 
Reported: 2006-02-23 12:41 EST by Nathan Kinder
Modified: 2015-12-07 12:14 EST (History)
2 users (show)

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


Attachments (Terms of Use)
CVS Diffs (1.15 KB, patch)
2006-02-23 12:45 EST, Nathan Kinder
no flags Details | Diff

  None (edit)
Description Nathan Kinder 2006-02-23 12:41:00 EST
When running setup of 64-bit Directory Server on my FC4 x86_64 machine, setup
complains that there is not enough available diskspace when I actually have
90+GB available on the installation partition.
Comment 1 Nathan Kinder 2006-02-23 12:45:51 EST
Created attachment 125120 [details]
CVS Diffs

We were using fscanf to read in the total unzipped size of our zip archives
incorrectly.  It was scanning for a normal int, but storing it in a long.  The
compiler was not automatically converting types correctly which would cause the
required space to be a huge number.  The proper thing to do is to have fscanf
read in a long.
Comment 2 Nathan Kinder 2006-02-23 12:52:41 EST
Checked into setuputil (HEAD).

Checking in product.cc;
/cvs/dirsec/setuputil/installer/unix/product.cc,v  <--  product.cc
new revision: 1.4; previous revision: 1.3
done

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