Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 6556bfde authored by Dirk Gouders's avatar Dirk Gouders Committed by David S. Miller
Browse files

netconsole.txt: revision of examples for the receiver of kernel messages 



There are at least 4 implementations of netcat with the BSD-based
being the only one that has to be used without the -p switch to
specify the listening port.

Jan Engelhardt suggested to add an example for socat(1).

Signed-off-by: default avatarDirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
Signed-off-by: default avatarCong Wang <amwang@redhat.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 6bdb7fe3

Documentation/networking/netconsole.txt

+17 −2
Original line number Diff line number Diff line
@@ -51,8 +51,23 @@ Built-in netconsole starts immediately after the TCP stack is 
initialized and attempts to bring up the supplied dev at the supplied

address.



The remote host can run either 'netcat -u -l -p <port>',

'nc -l -u <port>' or syslogd.

The remote host has several options to receive the kernel messages,

for example:



1) syslogd



2) netcat



   On distributions using a BSD-based netcat version (e.g. Fedora,

   openSUSE and Ubuntu) the listening port must be specified without

   the -p switch:



   'nc -u -l -p <port>' / 'nc -u -l <port>' or

   'netcat -u -l -p <port>' / 'netcat -u -l <port>'



3) socat



   'socat udp-recv:<port> -'



Dynamic reconfiguration:

========================