-
Bug
-
Resolution: Fixed
-
P1
-
solaris_10, 1.4.0, 1.4.0_01
-
02
-
x86, sparc
-
solaris_8, solaris_9, solaris_10
-
Not verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2053754 | 1.4.1 | Rajani Kaja | P1 | Closed | Fixed | beta |
After a Solaris 9 update one build two install, two files are left mode 666.
This is a result of the SUNWj3rt postinstall script, and the following code
touch $PREFS_LOCATION/.systemPrefs/.system.lock
touch $PREFS_LOCATION/.systemPrefs/.systemRootModFile
chmod 666 $PREFS_LOCATION/.systemPrefs/.systemRootModFile
chmod 666 $PREFS_LOCATION/.systemPrefs/.system.lock
The perms should be 644, with the owner being root. The latter
is probably true.
Also, any file added via a postinstall script in Solaris must be
added to the package data base via the installf command. See
other such additions in the same postinstall script.
Hopper should not go out (FCS) with this bug.
###@###.### 2002-05-20
This is a result of the SUNWj3rt postinstall script, and the following code
touch $PREFS_LOCATION/.systemPrefs/.system.lock
touch $PREFS_LOCATION/.systemPrefs/.systemRootModFile
chmod 666 $PREFS_LOCATION/.systemPrefs/.systemRootModFile
chmod 666 $PREFS_LOCATION/.systemPrefs/.system.lock
The perms should be 644, with the owner being root. The latter
is probably true.
Also, any file added via a postinstall script in Solaris must be
added to the package data base via the installf command. See
other such additions in the same postinstall script.
Hopper should not go out (FCS) with this bug.
###@###.### 2002-05-20
- backported by
-
JDK-2053754 system.lock and systemRootModFile have improper permissions.
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-