Bug 21892 - httpd active after a custom install
Summary: httpd active after a custom install
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apache
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Dale Lovelace
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-07 14:29 UTC by Giuseppe Raimondi
Modified: 2007-04-18 16:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-12-09 00:24:44 UTC
Embargoed:

Attachments (Terms of Use)

Description Giuseppe Raimondi 2000-12-07 14:29:21 UTC 
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?
Ciao
Comment 1 Daniel Roesen 2000-12-07 23:07:39 UTC 
Even if it's meant so, it's an unnecessary security risk.
Comment 2 Pekka Savola 2000-12-09 00:06:42 UTC 
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...
Comment 3 Bill Nottingham 2000-12-09 00:24:41 UTC 
Switching to an enhancement request, since having it on *is* the default behavior.
Comment 4 Nalin Dahyabhai 2001-01-11 19:41:14 UTC 
The init script is now disabled by default in 1.3.14-6 and newer.
Note You need to log in before you can comment on or make changes to this bug.