389-ds-base

#83 389-admin should use mod_cgid instead of mod_cgi
Closed: wontfix Opened by mkosek.

Closed: wontfix
Reopen Issue

https://bugzilla.redhat.com/show_bug.cgi?id=612564

Description of problem:
389-admin is improperly using the cgi module. When using a
multithreaded MPM (worker), mod_cgid had to be used. It happens that
389-admin needs apache (with worker MPM) and mod_cgi (and not
mod_cgid).
mod_cgid fork() itself from the main httpd process while mod_cgi
doesn't. That's why password_pipe() works fine with the latter.
Also see:
http://lists.fedoraproject.org/pipermail/389-users/2010-July/011710.html
http://httpd.apache.org/docs/2.2/mod/mod_cgid.html

batch update to FUTURE milestone

set default ticket origin to Community

Added initial screened field value.

Metadata Update from @rmeggins:
- Issue set to the milestone: 389-admin,console FUTURE

We do not wish to make changes to the admin at this point.

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to new (was: Needs Review)
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/83

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.
Metadata
None
None
None
None
Normal
new
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.