Bug 1006869 - init script: service restart under the nonroot changed behaviour, it returns 1 instead of 4
Summary: init script: service restart under the nonroot changed behaviour, it returns ...
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cronie
Version: 6.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Marcela Mašláňová
QA Contact: qe-baseos-daemons
Keywords: Regression
Depends On:
TreeView+ depends on / blocked
Reported: 2013-09-11 12:26 UTC by Petr Sklenar
Modified: 2016-03-01 14:40 UTC (History)
2 users (show)

Cause: Change of permission on confugration file /etc/sysconfig/crond showed a bug in initscript.

Consequence: The error message for non priviledged user was different.

Fix: Initscript has to check whether configuration file is readable by non root users.

Result: Error message looks like before.
Clone Of:
Last Closed: 2013-11-21 22:25:13 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1681 normal SHIPPED_LIVE cronie bug fix and enhancement update 2013-11-20 21:52:35 UTC

Description Petr Sklenar 2013-09-11 12:26:49 UTC
Description of problem:
service restart under the non root changed behaviour, it return 1 instead of 4

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
.qa.[root@x86-64-6s-m1 ~]# su - superman
[superman@x86-64-6s-m1 ~]$ service crond restart
User has insufficient privilege.
[superman@x86-64-6s-m1 ~]$ echo $?

rhel65 with cronie-1.4.4-11.el6.x86_64:
[superman@x86-64-6s-m1 ~]$ service crond restart
/etc/init.d/crond: line 37: /etc/sysconfig/crond: Permission denied
[superman@x86-64-6s-m1 ~]$ echo $?

Actual results:
error code = 1

Expected results:
error code = 4 

Additional info:

Comment 8 errata-xmlrpc 2013-11-21 22:25:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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