[Bug 757335] Documented command "service iptables save" fails

bugzilla at redhat.com bugzilla at redhat.com
Wed Feb 15 15:56:36 UTC 2012


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=757335

Emanuel Rietveld <codehotter at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |ASSIGNED
            Version|16                          |devel
                 CC|                            |codehotter at gmail.com,
                   |                            |eric at christensenplace.us,
                   |                            |oglesbyzm at gmail.com,
                   |                            |pkennedy at redhat.com,
                   |                            |security-guide-list at redhat.
                   |                            |com
          Component|iptables                    |security-guide
         AssignedTo|twoerner at redhat.com         |eric at christensenplace.us
         Resolution|DUPLICATE                   |
            Product|Fedora                      |Fedora Documentation
          QAContact|extras-qa at fedoraproject.org |docs-qa at lists.fedoraproject
                   |                            |.org
           Keywords|                            |Reopened

--- Comment #2 from Emanuel Rietveld <codehotter at gmail.com> 2012-02-15 10:56:34 EST ---
This should not be a duplicate of #748134 as it is a bug with the
documentation.

The guide at 
http://docs.fedoraproject.org/en-US/Fedora/16/html/Security_Guide/sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html 

still says "service iptables save" is how you save iptables rules. This should
be /usr/libexec/iptables.init save

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the docs-qa mailing list