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.
Bug 533895 - init script, restarting
Summary: init script, restarting
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rhnsd
Version: 6.0
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Miroslav Suchý
QA Contact: Šimon Lukašík
URL:
Whiteboard:
Depends On:
Blocks: 533839 633349
TreeView+ depends on / blocked
 
Reported: 2009-11-09 16:48 UTC by Petr Sklenar
Modified: 2010-09-13 16:16 UTC (History)
5 users (show)

Fixed In Version: rhnsd-4.9.2-2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-02 19:49:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Sklenar 2009-11-09 16:48:14 UTC
Description of problem:
A] su - nonroot; service rhnsd restart
B] try-restart

Version-Release number of selected component (if applicable):
rhnsd-4.7.0-4.el5

How reproducible:
always


A]
Steps to Reproduce:
[root@xen83 ~]# service rhnsd start
Starting Red Hat Network Daemon:                           [  OK  ]
[root@xen83 ~]# su - testuser
[testuser@xen83 ~]$ /etc/init.d/rhnsd restart
rm: cannot remove `/var/run/rhnsd.pid': Permission denied  [FAILED]

Starting Red Hat Network Daemon: 
touch: cannot touch `/var/lock/subsys/rhnsd': Permission denied
[testuser@xen83 ~]$ echo $?
0

Actual results:
restart like a nonroot return 0 when service is running and 1 when service is stopped

Expected results:
restart like a nonroot should return 4 in all cases

B]
Expected results:
try-restart have to be there and it should be same as condrestart

Additional info:
https://fedoraproject.org/wiki/Packaging/SysVInitScript

Comment 2 Miroslav Suchý 2010-02-10 13:26:04 UTC
Try-restart is implement for some time in spacewalk (commit d295180e5fbc3d49fd4891d9f2e36a9decaf0187)

the a] part has been fixed by commit ea34b43d2fd66b401c617748aa0379da4c5246db

Not cherrypicking to rhel6 as we will be rebasing within a month.

Comment 7 Šimon Lukašík 2010-04-27 11:52:52 UTC
Changing to VERIFIED

Testing procedure:
- general automation on i386, x86_64
- manual run on x86_64, RHEL6.0-20100422.12

Results of manual run:
- run as nonroot return 4 in all cases
- both condrestart & try-restart are implemented 
(same behaviour)

Verified against:
rhnsd-4.9.3-2.el6

Comment 8 releng-rhel@redhat.com 2010-07-02 19:49:17 UTC
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.


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