RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
1) "restart" action is not implemented in the init script
2) "status" action is implemented but not advertised when I run "service sandbox"

Version-Release number of selected component (if applicable):
policycoreutils-sandbox-2.0.82-14.el6

How reproducible:
always

Steps to Reproduce:

  
Actual results:


Expected results:

sandbox initrc script is not a standard init script.  It is just something that needs to be run at boot time.  It does not start a service, it just sets up the file system so tools like sandbox and xguest/mls environments can use pam_namespace

Unless Bill has a better location for this,  I think we have to close this as not a bug.

You could theoretically make it an upstart event, but that's probably overkill.

There seem to be two options for this bug: 

1) (preferred) Find better location for it. 
2) (easier) Despite the fact it is not a standard init script I think it would be good and easy to implement few actions required by init script quidelines. This is something we successfully accomplished in RHEL 6 init script project [1] for most components. 

Fedora guidelines for init scripts [2] provide details what is the minimum expected from this bug. But we definitely shouldn't close this bug as a not a bug. 

[1] http://wiki.test.redhat.com/BaseOs/Projects/InitScripts
[2] https://fedoraproject.org/wiki/Packaging/SysVInitScript

Fixed in policycoreutils-2.0.82-28.el6

Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.