[3252] in Kerberos-V5-bugs
krb5-appl/997: rcp man page bug
daemon@ATHENA.MIT.EDU (zacheiss@MIT.EDU)
Thu Sep 27 22:50:05 2001
Resent-From: gnats@rt-11.mit.edu (GNATS Management)
Resent-To: krb5-unassigned@rt-11.mit.edu
Resent-Reply-To: krb5-bugs@MIT.EDU, zacheiss@MIT.EDU
Message-Id: <200109280247.WAA11681@coleco-sidewinder.mit.edu>
Date: Thu, 27 Sep 2001 22:47:41 -0400 (EDT)
From: zacheiss@MIT.EDU
Reply-To: zacheiss@MIT.EDU
To: krb5-bugs@mit.edu
>Number: 997
>Category: krb5-appl
>Synopsis: -f flag should be documented in rcp man page
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: krb5-unassigned
>State: open
>Class: doc-bug
>Submitter-Id: unknown
>Arrival-Date: Thu Sep 27 22:50:00 EDT 2001
>Last-Modified:
>Originator: Garry Zacheiss
>Organization:
MIT
>Release: krb5-1.1.1 (and later)
>Environment:
System: SunOS coleco-sidewinder.mit.edu 5.8 Generic_108528-08 sun4u sparc SUNW,Sun-Blade-100
Architecture: sun4
>Description:
The rcp man page does not document the -f flag, which is what
the server side rcp runs. This in and of itself isn't a
problem, except -f is overloaded in some people's minds to mean
"forward tickets", causing some users to rcp -f and then wonder
why their rcp is hanging forever.
>How-To-Repeat:
rcp -f /etc/passwd root@host:/etc/passwd
Scratch head.
>Fix:
The rcp man page should list the -f flag along with some
explanatory text stating "this doesn't do what you think it
does".
>Audit-Trail:
>Unformatted:
