Bug 161776 - telnet man page has a formatting problem
telnet man page has a formatting problem
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: krb5 (Show other bugs)
4.0
All Linux
medium Severity low
: ---
: ---
Assigned To: Nalin Dahyabhai
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-27 05:15 EDT by David Tonhofer
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: 1.3.4-13
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-06 09:59:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Tonhofer 2005-06-27 05:15:43 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:
Typing 'man telnet' just gives you unformatted garbage like this:

-------------
        .           .          .          .          .          .          .          .          .          .          .          .          .
        .          .          .          .          .          .          .          .          .          .          .TH TELNET 1         .SH
NAME          telnet  − user interface to the TELNET protocol         .SH SYNOPSIS         .B telnet         [−8] [−E] [−F] [−K] [−L] [−S tos]
[−X authtype] [−a] [−c] [−d] [−e escapechar] [−f] [−k realm] [−l user] [−n tracefile] [−r] [−x] [host [port]] The command is used to  communi-
cate  with  another  host  using  the protocol.  If is invoked without the argument, it enters command mode, indicated by its prompt ( In this
-------------

However, the file /usr/share/man/man1/telnet.1.gz looks like properly 
formatted groff, also "less /usr/share/man/man1/telnet.1.gz" automagically
formats everything correctly. 



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


How reproducible:
Always

Steps to Reproduce:
n/a
  

Actual Results:  n/a

Expected Results:  n/a

Additional info:

n/a
Comment 1 Harald Hoyer 2005-09-02 11:06:46 EDT
what is the output of:
# man -aw telnet

??
Comment 2 David Tonhofer 2005-09-02 12:04:15 EDT
It might just be that the problem has been fixed. On a RH ES 4 system that
has not be updated in a long time, the problem occurs as described:

# man -aw telnet
/usr/kerberos/man/man1/telnet.1.gz
/usr/share/man/man1/telnet.1.gz
# rpm --query telnet
telnet-0.17-30
# uname -a
Linux foo 2.6.9-5.0.3.ELsmp #1 SMP Mon Feb 14 10:00:21 EST 2005 x86_64 x86_64
x86_64 GNU/Linux

On a recently updated system ,the problem does no longer occur:
# man -aw telnet
/usr/kerberos/man/man1/telnet.1.gz
/usr/share/man/man1/telnet.1.gz
# rpm --query telnet
telnet-0.17-31.EL4.3
# uname -a
Linux bar 2.6.9-11.ELsmp #1 SMP Fri May 20 18:25:30 EDT 2005 x86_64 x86_64
x86_64 GNU/Linux
Comment 3 Harald Hoyer 2005-09-05 01:48:57 EDT
try this:
# man /usr/kerberos/man/man1/telnet.1.gz
# man /usr/share/man/man1/telnet.1.gz
Comment 4 David Tonhofer 2005-09-05 04:51:32 EDT
On the older system where "man telnet" gives unformatted output:

# man /usr/kerberos/man/man1/telnet.1.gz  --> Unformatted
# man /usr/share/man/man1/telnet.1.gz     --> Formatted

Ah-ha. 

($MANPATH is currently
 "/usr/java/jdk/man::/usr/local/apache2/man:/usr/local/mysql/man"
 $LANG on both systems is en_US.UTF-8)

On the newer system where "man telnet" gives formatted output:

# man /usr/kerberos/man/man1/telnet.1.gz  --> Formatted
# man /usr/share/man/man1/telnet.1.gz     --> Formatted

Right. The 'man telnet' page is indeed the kerberos manpage on
both systems as it mentions 'k5login' among others.
Comment 5 Harald Hoyer 2005-09-05 12:09:12 EDT
$ rpm -qf /usr/kerberos/man/man1/telnet.1.gz
krb5-workstation-1.4-3
Comment 6 Nalin Dahyabhai 2005-09-06 09:59:17 EDT
David, I think the update which corrected this for you was
krb5-workstation-1.3.4-13, which incorporated the fix from bug #120618.  Closing
as fixed in current release because an updated system has the fix.

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