Bug 753834 - Init scripts are written to assume there is only one instance of service
Summary: Init scripts are written to assume there is only one instance of service
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: distribution
Version: 4.9
Hardware: All
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: RHEL Program Management
QA Contact: Radek Bíba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-14 16:16 UTC by Anton
Modified: 2012-06-20 16:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 16:00:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Anton 2011-11-14 16:16:44 UTC
Description of problem:
It's mostly openvz related problem.
OpenVZ host sees all daemons running inside containers. Init script on host system kills all instances of service.

Version-Release number of selected component (if applicable):
RHEL 4,5,6

How reproducible:
Always.

Steps to Reproduce:
1.Setup openvz container.
2.Start same service on host and inside VE for example ntpd.
3.Stop service on host system.
  
Actual results:
Daemon running inside container is stopped.

Expected results:
Host's init scripts don't hurt processes inside containers.

Additional info:
It's also applicable to more than one instance of service running on same system.
Some of scripts are killing processes by name not by pid. It causes such problems.

Comment 1 Jiri Pallich 2012-06-20 16:00:50 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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