Document the possible use of eval.

diff --git a/dhcpcd.8.in b/dhcpcd.8.in
index 1c136887a8316dc97af3e8afb6bd23f34dc9fd4f..92582f4eab522358d066a241f05f3f73c19094dc 100644 (file)
--- a/dhcpcd.8.in
+++ b/dhcpcd.8.in
@@ -218,7 +218,8 @@ or
 .Pp
 .Nm
 sanitises each string variable passed from the DHCP/RA message by encoding non
-printable characters in escaped octal and escaping the following characters:
+printable characters in C style where possible, or escaped octal when not.
+The following characters are also escaped in C style (except for $ in octal):
 .D1 | \*[Am] \&; \*[Lt] \*[Gt] \&( \&) $ ` \e \*q ' \
 \*[Lt]tab\*[Gt] \*[Lt]newline\*[Gt]
 .D1 * \&? \&[ # ~ = %
@@ -237,6 +238,15 @@ character octal escaped and C style encoding you can do this:
 .D1 dhcpcd-decode -s \*q$variable-name\*q
 or
 .D1 printf \*q%s\*q \*q$variable_name\*q | unvis | vis -c
+.Pp
+If you have neither
+.Xr dhcpcd-decode 8
+or a working
+.Xr unvis 1 ,
+then the shell builtin eval could be used:
+.D1 eval \*q$variable_name\*q
+but that does not work well with any non printable characters and the $
+character.
 .Ss Fine tuning
 You can fine-tune the behaviour of
 .Nm