This is an automated email from Gerrit. Peter Bigot ([email protected]) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/3638
-- gerrit commit 878bc607a8cf2220ce90d31d00329f70f9f524c9 Author: Peter A. Bigot <[email protected]> Date: Wed Aug 10 16:58:07 2016 -0500 doc: correct and standardize instructions for disabling TCP servers The instructions to set the port to zero to disable a service has not worked for several years: the effect of doing so is to start the service on a port randomly selected by the bind(2) system call. Update the documentation to reflect the new standard way of disabling network services. Change-Id: Ic5315a80f9956ea195f63e05d30d604a980bbc8f Signed-off-by: Peter A. Bigot <[email protected]> diff --git a/doc/openocd.texi b/doc/openocd.texi index 983ce3c..814d4f4 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -2097,7 +2097,7 @@ only during configuration (before those ports are opened). For reasons including security, you may wish to prevent remote access using one or more of these ports. -In such cases, just specify the relevant port number as zero. +In such cases, just specify the relevant port number as "disabled". If you disable all access through TCP/IP, you will need to use the command line @option{-pipe} option. @@ -2140,7 +2140,7 @@ output from the Tcl engine. Intended as a machine interface. When not specified during the configuration stage, the port @var{number} defaults to 6666. - +When specified as "disabled", this service is not activated. @end deffn @deffn {Command} telnet_port [number] @@ -2149,7 +2149,7 @@ port on which to listen for incoming telnet connections. This port is intended for interaction with one human through TCL commands. When not specified during the configuration stage, the port @var{number} defaults to 4444. -When specified as zero, this port is not activated. +When specified as "disabled", this service is not activated. @end deffn @anchor{gdbconfiguration} -- ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
