Closed Bug 8549 Opened 27 years ago Closed 27 years ago

component.reg needs to be writeable for apprunner to start

Categories

(Core :: XPCOM, defect, P3)

Sun
Solaris
defect

Tracking

()

VERIFIED DUPLICATE of bug 9120

People

(Reporter: tor, Assigned: dp)

Details

Description: apprunner opens component.reg O_RDWR, which will fail if the mozilla installation directory is on a read-only filesystem. Will probably also fail to run on a read-write filesystem if someone other than the installer tries to run apprunner. Steps to reproduce: Copy dist/bin to a read-only filesystem, then run apprunner. Actual results: apprunner quietly dies after spitting out these messages: Registered Ok *** Registering html library Expected results: apprunner starting normally. Build date & platform: 6/19/99 build on Solaris Additional information: % truss ./apprunner | & fgrep component.reg open64("/cs/lib/mozilla/component.reg", O_RDWR|O_CREAT, 0644) Err#30 EROFS open64("/cs/lib/mozilla/component.reg", O_RDWR|O_CREAT, 0644) Err#30 EROFS open64("/cs/lib/mozilla/component.reg", O_RDWR|O_CREAT, 0644) Err#30 EROFS open64("/cs/lib/mozilla/component.reg", O_RDWR|O_CREAT, 0644) Err#30 EROFS
Status: NEW → ASSIGNED
Target Milestone: M9
This is true. The first time you run apprunner, component.reg will be written to. The hope is that this is equivalent to the installation step and once we have an installer would go away. On subsequent runs, components.reg should be READONLY. And should be opened so. The fact that it always open for RDWR is a bug.
Target Milestone: M9 → M10
Target Milestone: M10 → M11
Status: ASSIGNED → RESOLVED
Closed: 27 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 9120 ***
[bugday] This bug deals with the same file that the other does.
Status: RESOLVED → VERIFIED
Component: XPCOM Registry → XPCOM
QA Contact: dp → xpcom
You need to log in before you can comment on or make changes to this bug.