Bug 1391434

Summary: systemctl start smbd => systemctl start smb
Product: Red Hat Enterprise Linux 7 Reporter: François Cami <fcami>
Component: doc-Windows_Integration_GuideAssignee: Aneta Šteflová Petrová <apetrova>
Status: CLOSED CURRENTRELEASE QA Contact: Kaushik Banerjee <kbanerje>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: kludhwan, rhel-docs, tscherf
Target Milestone: rcKeywords: Documentation, EasyFix, Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-24 06:42:05 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:

Description François Cami 2016-11-03 10:28:03 UTC
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/Windows_Integration_Guide/creating-trusts.html#trust-set-up-idm

Section Number and Name: 
5.3.3.1. Preparing the IdM Server for Trust

Describe the issue: 
[root@ipaserver ~]# systemctl start smbd
should be
[root@ipaserver ~]# systemctl start smb

Comment 1 Aneta Šteflová Petrová 2016-11-03 11:16:53 UTC
I fixed the command.

Comment 4 François Cami 2016-11-03 12:18:46 UTC
Note: upstream documentation is OK:
http://www.freeipa.org/page/Active_Directory_trust_setup

Comment 5 Aneta Šteflová Petrová 2016-11-04 08:39:35 UTC
The updated content is now available on the Customer Portal.

Comment 6 Aneta Šteflová Petrová 2016-11-04 08:51:37 UTC
Sorry for the confusion, this fix has not yet been published.

Comment 7 Aneta Šteflová Petrová 2016-11-04 08:55:38 UTC
*** Bug 1391655 has been marked as a duplicate of this bug. ***

Comment 8 Aneta Šteflová Petrová 2016-11-22 15:59:04 UTC
*** Bug 1397453 has been marked as a duplicate of this bug. ***

Comment 9 Aneta Šteflová Petrová 2016-11-24 06:42:05 UTC
Published in an asynchronous update. The content is now available on the Customer Portal.