Bug 1093726

Summary: manpage for tc needs info on filters
Product: Red Hat Enterprise Linux 6 Reporter: Jeremy Harris <jeharris>
Component: iprouteAssignee: Phil Sutter <psutter>
Status: CLOSED ERRATA QA Contact: Jaroslav Aster <jaster>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.5CC: jaster, kzhang, mmarusic, rkhan, thozza
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: iproute-2.6.32-47.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1286711 (view as bug list) Environment:
Last Closed: 2016-05-11 00:18:55 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1172231, 1275424    

Description Jeremy Harris 2014-05-02 13:19:20 UTC 
Description of problem:
  Specifically, there is nothing on handles or cgroups.  The See-Also doc site (http://lartc.org) has not at all on cgroups.


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

  2.6.32-431.3.1.el6.x86_64

  The tc manpage last line is:
"iproute2                       16 December 2001                          TC(8)"

How reproducible:
  Always


Steps to Reproduce:
1.  Attempt to learn how stuff works
2.  Fail
3.

Actual results:
  No Info

Expected results:
  In the "tc" manpage: See-Also links, or embedded info, for specifics for all the available filters.

  A Resource Management Guide chapter on tc would also be good.

Additional info:
  There's a link in the reverse direction, from cgroups to tc, in the Resource_Management_Guide (section 3.8: net_cls), which suggests the tc manpage.
Comment 5 Phil Sutter 2015-10-29 08:58:07 UTC 
A patch series adding man pages for filters has been sent upstream and accepted: http://thread.gmane.org/gmane.linux.network/384390
Comment 10 errata-xmlrpc 2016-05-11 00:18:55 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0895.html