Bug 172816 - use system perl for AS PERL5; make files owned by AS uid
Summary: use system perl for AS PERL5; make files owned by AS uid
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: 389
Classification: Retired
Component: Admin
Version: 7.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: 152373 240316
TreeView+ depends on / blocked
 
Reported: 2005-11-10 00:53 UTC by Rich Megginson
Modified: 2015-12-07 16:55 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-07 16:55:10 UTC
Embargoed:


Attachments (Terms of Use)
Files fixed (67 bytes, text/plain)
2005-11-10 00:53 UTC, Rich Megginson
no flags Details
Diffs for fix (3.89 KB, text/plain)
2005-11-10 00:54 UTC, Rich Megginson
no flags Details

Description Rich Megginson 2005-11-10 00:53:51 UTC
Created attachment 120863 [details]
Files fixed

Comment 1 Rich Megginson 2005-11-10 00:53:51 UTC
1) Allow the use of the system perl on all linuxes (like the recent fix for
adminutil).  This is primarily to allow the build on FC.
2) Make sure admpw, console.conf, and adm.conf are owned by the SSuser which is
the uid of the admin server process.  Otherwise, no console tasks work, and most
CGIs fail as well.

Comment 2 Rich Megginson 2005-11-10 00:54:22 UTC
Created attachment 120864 [details]
Diffs for fix

Comment 3 Rich Megginson 2005-11-10 01:09:54 UTC
Reviewed by: Noriko (Thanks!)
Files: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=120863
Branch: HEAD
Fix Description: 1) I made a similar fix to adminutil to use the system 
perl for the PERL5 macro on all Linux systems.  2) The files admpw, 
adm.conf, and console.conf are read and/or written by the httpd process, 
which is owned by the SSuser (default nobody), so they must be owned by 
that user.
Platforms tested: FC4
Flag Day: no
Doc impact: no
QA impact: should be covered by regular nightly and manual testing
New Tests integrated into TET: none


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