Bug 1039465 - Consider replacing 'exit 0' in rc.local with 'true'
Summary: Consider replacing 'exit 0' in rc.local with 'true'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-09 08:09 UTC by Marian Csontos
Modified: 2014-06-18 00:36 UTC (History)
3 users (show)

Fixed In Version: systemd-207-9.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 11:33:54 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Marian Csontos 2013-12-09 08:09:05 UTC 
Description of problem:
'exit 0' in rc.local breaks any script who attempts to append to it.

What is the rationale behind the change?

This change is incompatible with previous releases and should be treated with due care.

Version-Release number of selected component (if applicable):
systemd-207-8.el7.x86_64

Actual results:
rc.local skips appended sections

Expected results:
rc.local should run everything there is
Comment 2 Lukáš Nykrýn 2013-12-09 14:38:28 UTC 
(In reply to Marian Csontos from comment #0)
> What is the rationale behind the change?
> 
> This change is incompatible with previous releases and should be treated
> with due care.
rc.local behaves quite differently from rhel6, so my intent was that administrator should read the warning in comments in this file.

But the proposal make sense, just please note that you still need to run chmod +x.
Comment 3 Lukáš Nykrýn 2013-12-13 12:16:28 UTC 
After some thinking, we have this file for backward compatibility, so it would maybe make sense to use "touch /var/lock/subsys/local" again.
Comment 6 Ludek Smid 2014-06-13 11:33:54 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.