Bug 1027489 - Firewalld documentation on wiki incorrect for enable-panic, disable-panic. Should be panic-on, panic-off.
Summary: Firewalld documentation on wiki incorrect for enable-panic, disable-panic. Sh...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: fedora-websites
Version: devel
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: Fedora Websites Team
QA Contact: Fedora Websites Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-06 23:09 UTC by gregjo
Modified: 2013-11-11 22:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-11 22:47:07 UTC


Attachments (Terms of Use)

Description gregjo 2013-11-06 23:09:31 UTC
Description of problem:
The documentation for FirewallD on this wiki page:
https://fedoraproject.org/wiki/FirewallD
states that the Panic Options should use
--enable-panic
--disable-panic
however the correct options (see: 'man firewall-cmd') are:
--panic-on
--panic-off


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

How reproducible:
Always

Steps to Reproduce:
1. Type 'man firewall-cmd' and note the proper Panic options are '--panic-on' and '--panic-off'.
2. Note the wiki page referenced above. It still documents '--enable-panic' and '--disable-panic'.


Actual results:
Using the command: 'firewall-cmd --enable-panic' results in the following:
firewall-cmd: error: unrecognized arguments: --enable-panic

Expected results:
The documentation on the wiki page should correctly state that the options are '--panic-on' and '--panic-off'.


Additional info:
According to this change in the source:
https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=df08c08dfd9fa0ea366fd9d4d2b043d2ae7027c3
the options should be:
--panic-on
--panic-off

Comment 1 Ian Weller 2013-11-11 22:47:07 UTC
Thanks for the report.

https://fedoraproject.org/w/index.php?title=FirewallD&diff=360437&oldid=357485


Note You need to log in before you can comment on or make changes to this bug.