Bug 63565 - Unexpected stderr output from "man 8 rpc.yppasswdd" command
Summary: Unexpected stderr output from "man 8 rpc.yppasswdd" command
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ypserv
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-15 18:13 UTC by Glen A. Foster
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-04-15 20:07:38 UTC
Embargoed:

Attachments (Terms of Use)

Description Glen A. Foster 2002-04-15 18:13:54 UTC 
Description of Problem: Something is not right with the rpc.yppasswdd.8
man-page.  If you run the command "man 8 rpc.yppasswdd 2> stderr", there's data
in the file "stderr".

Version-Release number of selected component (if applicable):
# rpm -qf $(which rpc.yppasswdd)
ypserv-1.3.12-2

How Reproducible: 100%

Steps to Reproduce:
1. man 8 rpc.yppasswdd 2> stderr

Actual Results: contents are as follows:
# cat stderr
/usr/share/groff/1.17.2/font/devlatin1/.:0: error: missing charset command

Expected Results: empty stderr output
Comment 1 Glen A. Foster 2002-04-15 18:14:31 UTC 
... same results checking "yppasswdd" man-page
Comment 2 Alexander Larsson 2002-04-15 18:30:52 UTC 
I don't get this with ypserv-2.2-6, but it looks like the bug is actually in
some groff config file or something. Could you upgrade to The ypserv from
rawhide and see if you still get this.
Comment 3 Glen A. Foster 2002-04-15 20:07:33 UTC 
Upgrading to rawhide version (ypserv-2.2-8) eliminates the problem.  Don't know 
about the "groff is the culprit" portion, though.
Comment 4 Alexander Larsson 2002-04-15 20:48:16 UTC 
Then i'm closing this bug RAWHIDE. 

There will eventually (in a month or so) be an yp errata for older versions of
Red Hat to fix various deficiencies. So you can opt to wait for that too.
Note You need to log in before you can comment on or make changes to this bug.