Bug 348891 - pam_namespace use of namespace.init needs to be configurable per directory
pam_namespace use of namespace.init needs to be configurable per directory
Status: CLOSED NEXTRELEASE
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pam (Show other bugs)
5.1
All Linux
low Severity high
: ---
: ---
Assigned To: Tomas Mraz
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-10-23 11:17 EDT by Ted X Toth
Modified: 2008-06-03 05:53 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-06-03 05:53:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ted X Toth 2007-10-23 11:17:07 EDT
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 05:53:47 EDT
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.