Attachment 575733 Details for Bug 675441 – Patch for rexec.1 Fedora 16

[patch] Patch for rexec.1 Fedora 16

rexec_1_20120406.patch (text/plain), 1.79 KB, created by John Bradshaw on 2012-04-06 12:52:59 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: John Bradshaw

Created: 2012-04-06 12:52:59 UTC

Size: 1.79 KB

patch

obsolete

>--- rexec.1	2012-04-06 13:48:32.520275688 +0100
>+++ rexec.new	2012-04-06 13:51:49.264839665 +0100
>@@ -95,7 +95,7 @@
> Use signal handling as in BSD rsh(1).  Only the signals 
> SIGINT, SIGQUIT, and SIGTERM are echoed to the remote process.
> They do not remain raised locally, so rexec waits for the
>-remote command to shutdown its side of the socket.  Also, CNTRL-Z will
>+remote command to shutdown its side of the socket.  Also, CTRL-Z will
> only suspend execution locally--the remote command may continue to run.
> .TP
> \fB\-c\fP
>@@ -113,7 +113,7 @@
> \fB\-s\fP
> Do not echo signals received by the rexec onto the remote
> process.  Normally, signals which can be trapped are passed
>-on to the remote process; then, when you type CNTRL-C, the remote
>+on to the remote process; then, when you type CTRL-C, the remote
> process terminates as well.
> .SH USERNAME AND PASSWORD
> .B Rexec(1)
>@@ -139,12 +139,12 @@
> .B rexec(3)
> transmits their password to the remote host clear text, not
> encrypted.  If the network is not secure to the remote host, the
>-password can be comprimised.
>+password can be compromised.
> 
> .SH SIGNALS
> Without the -b option,
> all signals which can be handled are echoed to the remote process.
>-Afterwards, however, they remain raised in the local process.  
>+Afterward, however, they remain raised in the local process.  
> Typically, this means that 
> .B rexec(1)
> will exit after receiving a fatal signal, even if the remote
>@@ -153,7 +153,7 @@
> Differing operating systems use differing signal numbers; for example
> AIX and SunOS use 18 for SIGTSTP (^Z), while Linux uses 20.  Therefore, 
> it may have a different effect remotely than
>-locally.  In particular, typing CNTL-Z may not suspend the execution
>+locally.  In particular, typing CTRL-Z may not suspend the execution
> of the remote process.
> .SH EXAMPLE
> .PP

Actions: View | Diff

Attachments on bug 675441: 477221 | 575733