Red Hat Bugzilla – Bug 21892
httpd active after a custom install
Last modified: 2007-04-18 12:30:09 EDT
After a custom/everything install on a test machine httpd is starting at
boot. I didn't try to configure it, was just the default setting. Is it
meant to be so?
Even if it's meant so, it's an unnecessary security risk.
Services that are installed are considered to be enabled with certain exceptions
(most of those launched from xinetd). Perhaps not the best policy, but simple on
the package installer...
Switching to an enhancement request, since having it on *is* the default behavior.
The init script is now disabled by default in 1.3.14-6 and newer.