Bug 348891 - pam_namespace use of namespace.init needs to be configurable per directory
Summary: pam_namespace use of namespace.init needs to be configurable per directory
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pam
Version: 5.1
Hardware: All
OS: Linux
low
high
Target Milestone: ---
: ---
Assignee: Tomas Mraz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-23 15:17 UTC by Ted X Toth
Modified: 2008-06-03 09:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-03 09:53:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ted X Toth 2007-10-23 15:17:07 UTC
Description of problem:
If the file /etc/security/namespace.init exists it will be exec'd for every
directory being polyinstantiated. I'm currently polyinstantiating about 30
directories and the overhead of these execs has become a major performance
problem especially in light of the fact that I really only need namespace.init
run for /tmp.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
 I've patched pam_namespace to use a configuration option run_init/no_init to
have finer control over the use of the namespace.init script.

Comment 1 Tomas Mraz 2008-06-03 09:53:47 UTC
This bug will be fixed in the next major release of Red Hat Enterprise Linux.



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