Bug 976101 - typo in Security Guide 3.9.3 - should be /sbin/service iptables
Summary: typo in Security Guide 3.9.3 - should be /sbin/service iptables
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: security-guide
Version: devel
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Eric Christensen
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-19 22:21 UTC by Bob
Modified: 2013-09-12 03:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-12 03:02:19 UTC
Embargoed:

Attachments (Terms of Use)
Patch swapping the words around. (1.40 KB, patch)
2013-06-19 23:48 UTC, Eric Christensen 		sparks: review?
Details | Diff
View All

Description Bob 2013-06-19 22:21:31 UTC 
Description of problem:
typo in Security Guide section 3.9.3 - incorrect in final Note "(/sbin/iptables service)" should be "(/sbin/service iptables)"

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

How reproducible:
Always.

Steps to Reproduce:
1. Read section 3.9.3
2.
3.

Actual results:
(/sbin/iptables service)

Expected results:
(/sbin/service iptables)

Additional info:
It is correct elsewhere on the page.
Comment 1 Eric Christensen 2013-06-19 23:48:56 UTC 
Created attachment 763174 [details]
Patch swapping the words around.

Does this fix this?
Comment 2 Bob 2013-06-21 00:48:10 UTC 
(In reply to Eric Christensen from comment #1)
> Created attachment 763174 [details]
> Patch swapping the words around.
> 
> Does this fix this?

Yes!  Thanks.
Comment 3 Chris Roberts 2013-06-21 08:54:43 UTC 
Looks good Bob
Comment 4 Eric Christensen 2013-09-12 03:02:19 UTC 
commit fe1ab6505255a1ca64a8eb9600ced2fd9588a4f3
Author: Eric \"Sparks\" Christensen <sparks>
Date:   Wed Jun 19 19:46:42 2013 -0400

    Fixed command error per BZ 976101
    
    Signed-off-by: Eric "Sparks" Christensen <sparks>
Note You need to log in before you can comment on or make changes to this bug.