Bug 63544

Summary: Unexpected stderr output from "man 1 nc" command
Product: [Retired] Red Hat Linux Reporter: Glen A. Foster <glen.foster>
Component: ncAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-06-12 06:53:17 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 Glen A. Foster 2002-04-15 17:32:35 UTC 
Description of Problem: Something is not right with the nc.1 man-page.  If you
run the command "man 1 nc 2> stderr", there's data in the file "stderr".

Version-Release number of selected component (if applicable):
# rpm -q $(which nc)
nc-1.10-11

How Reproducible: 100%

Steps to Reproduce:
1. man 1 nc 2> stderr

Actual Results: contents are as follows:
# cat stderr
mdoc warning: list open at EOF!  A .Bl directive has no matching .El

Expected Results: empty stderr output
Comment 1 Bill Nottingham 2002-07-19 01:17:09 UTC 
Fixed in 1.10-15.