Bug 63560 - Unexpected stderr output from "man 8 nslookup" command
Unexpected stderr output from "man 8 nslookup" command
Product: Red Hat Linux
Classification: Retired
Component: bind (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: wdovlrrw
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-04-15 14:09 EDT by Glen A. Foster
Modified: 2007-04-18 12:42 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-04-15 14:09:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Glen A. Foster 2002-04-15 14:09:33 EDT
Description of Problem: Something is not right with the nslookup.8 man-page.  If
you run the command "man 8 nslookup 2> stderr", there's data in the file

Version-Release number of selected component (if applicable):
# rpm -qf $(which nslookup)

How Reproducible: 100%

Steps to Reproduce:
1. man 8 nslookup 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

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