From eceaee3431e01f9d2668b0be40a60681ebb734c3 Mon Sep 17 00:00:00 2001 From: Jan Engelhardt Date: Sat, 25 Jun 2011 00:05:26 +0200 Subject: [PATCH] doc: do not advertise old tools Remove mention of netcat from the libxt_SYSRQ manpage. --- extensions/libxt_SYSRQ.man | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/extensions/libxt_SYSRQ.man b/extensions/libxt_SYSRQ.man index 5470066..ab230a8 100644 --- a/extensions/libxt_SYSRQ.man +++ b/extensions/libxt_SYSRQ.man @@ -54,7 +54,7 @@ The xt_SYSRQ module is normally silent unless a successful request is received, but the \fIdebug\fP module parameter can be used to find exactly why a seemingly correct request is not being processed. .PP -To trigger SYSRQ from a remote host, just use netcat or socat: +To trigger SYSRQ from a remote host, just use socat: .PP .nf sysrq_key="s" # the SysRq key(s) @@ -67,8 +67,6 @@ req="$sysrq_key,$seqno,$salt" req="$req,$(echo \-n "$req,$ipaddr,$password" | sha1sum | cut \-c1\-40)" echo "$req" | socat stdin udp\-sendto:$ipaddr:9 -# or -echo "$req" | netcat \-uw1 $ipaddr 9 .fi .PP See the Linux docs for possible sysrq keys. Important ones are: re(b)oot,