From bc6940585f5f394c8c3fcff58c764a40f7294d4b Mon Sep 17 00:00:00 2001 From: Benedict Reuschling Date: Mon, 26 Jul 2010 18:33:33 +0000 Subject: [PATCH] Use "printf" instead of "echo -n" in an example because it should be more compatible for most shells that are out there. I contacted Philip Guenther at OpenBSD about this PR and he corrected the issue in their tree pretty fast. PR: docs/142243 Submitted by: Yasir (yasir27 at mail dot ru) Obtained from: OpenBSD Discussed with: delphij MFC after: 7 days --- contrib/netcat/nc.1 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contrib/netcat/nc.1 b/contrib/netcat/nc.1 index ac6aa475fbd7..41f5f092cdee 100644 --- a/contrib/netcat/nc.1 +++ b/contrib/netcat/nc.1 @@ -27,7 +27,7 @@ .\" .\" $FreeBSD$ .\" -.Dd April 15, 2010 +.Dd July 3, 2010 .Dt NC 1 .Os .Sh NAME @@ -340,7 +340,7 @@ when it might be necessary to verify what data a server is sending in response to commands issued by the client. For example, to retrieve the home page of a web site: .Bd -literal -offset indent -$ echo -n "GET / HTTP/1.0\er\en\er\en" | nc host.example.com 80 +$ printf "GET / HTTP/1.0\er\en\er\en" | nc host.example.com 80 .Ed .Pp Note that this also displays the headers sent by the web server.