Bug 63544 - Unexpected stderr output from "man 1 nc" command
Summary: Unexpected stderr output from "man 1 nc" command
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: nc
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-15 17:32 UTC by Glen A. Foster
Modified: 2014-03-17 02:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-06-12 06:53:17 UTC
Embargoed:


Attachments (Terms of Use)

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.


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