Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1378590

Summary: Incorrect example in systemd documentation
Product: Red Hat Enterprise Linux 7 Reporter: Paulo Andrade <pandrade>
Component: doc-System_Administrators_GuideAssignee: Maxim Svistunov <msvistun>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: high    
Version: 7.2CC: lnykryn, myamazak, pandrade, rhel-docs
Target Milestone: rcKeywords: Documentation, EasyFix
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-11 08:08:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paulo Andrade 2016-09-22 20:06:34 UTC 
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sect-Managing_Services_with_systemd-Unit_Files.html#Overriding_Unit_Mod-Change-timout-limit

Describe the issue:
Documentation says the command to change the default is:
echo '[Service] TimeoutStartSec=10' > /etc/systemd/system/network.service.d/timeout.conf
but the parser will not understand it, must add a newline.
Correct command would be:
echo '[Service]\nTimeoutStartSec=10' > /etc/systemd/system/network.service.d/timeout.conf

The problem is present for all translations.
Comment 3 Paulo Andrade 2016-09-23 12:17:46 UTC 
  Bad cut&paste, please note that the correct example
would be:

echo -e '[Service]\nTimeoutStartSec=10' > /etc/systemd/system/network.service.d/timeout.conf

otherwise the "\n" would not be correctly handled.
Comment 4 Paulo Andrade 2016-09-27 15:10:53 UTC 
  There is also a typo in the title

"Changing the timout limit"

and another issue is that the documentation tells that
the default timeout is 5min. A 5min timeout is default
for sysv wrapped/compat services. Systemd managed services
default to 90s timeout, so the documentation should be
update to tell the default is 90s, but have a note about
the sysv compat services that have a default of 5min
(that are very few in rhel7, but "network" is the most
notable).