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 770195

Summary: Section 32.4 - Kickstart options for "firewall" keyword is incorrect
Product: Red Hat Enterprise Linux 6 Reporter: Kwan Lowe <kwan>
Component: doc-Installation_GuideAssignee: Jack Reed <jreed>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0CC: jskeoch, pbokoc
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-25 23:34:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kwan Lowe 2011-12-24 01:59:29 UTC
Description of problem:
Many of the kickstart options are missing BNF notation of syntax. For example, the iscsi, logging and monitor keywords do not have BNFs. This is inconsistent with the rest of the section.




How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
The text from the "logging" section, for example:
logging (optional)
This command controls the error logging of anaconda during installation. It has no effect on the installed system.
--host= — Send logging information to the given remote host, which must be running a syslogd process configured to accept remote logging.
--port= — If the remote syslogd process uses a port other than the default, it may be specified with this option.
--level= — One of debug, info, warning, error, or critical.
Specify the minimum level of messages that appear on tty3. All messages will still be sent to the log file regardless of this level, however.
Version-Release number of selected component (if applicable):

Expected results:

logging [--host=<host>] [--port=<port>] [--level= "debug"|"info" ] 

( :)  The BNF above is not "correct" either )

Additional info:

Comment 2 Jack Reed 2012-03-06 03:26:08 UTC
Due to time constraints, pushing to 6.4 because this is a fairly meticulous formatting issue.

Comment 3 Jack Reed 2012-10-19 03:11:42 UTC
Thanks very much for reporting this. I can certainly see the inconsistency.

For the 6.4 documentation, I've added BNF notation to the three you've mentioned: iscsi, monitor, and logging, especially because they were the three most in need of tidying up (iscsi in particular). 

I can see there are a few other candidates, and I will fix them up as time commitments allow.

Here's the new notation I've added:

iscsi --ipaddr=<ipaddr> [options]
logging [--host=<host>] [--port=<port>] [--level=debug|info|error|critical]
monitor --monitor=<monitorname>|--hsync|vsync=<frequency> [--noprobe]

Comment 6 Jack Reed 2013-02-25 23:34:08 UTC
This bug has been verified and implemented for 6.4, so I am changing the status to CLOSED CURRENT RELEASE.