literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
constructions that parse out to [ -z "$foo" ] && foo=""
These are bad examples that get copied and pasted into new code, so the
hope is that with less bad examples there will be less need for me to
bring this up in review.
In a few of these files all that were changed were comments so that next
time I search for these patterns I won't trip on the file for no reason.
In a few places, add $FreeBSD$
No functional changes, so no PORTREVISION bumps
proxy or proxies (host1..N and port1..N) and opens a listening socket,
forwarding each request to the parent proxy (moving in a circular list if the
active parent stops working). Along the way, a connection to the parent is
created anew and authenticated or, if available, previously cached connection
is reused to achieve higher efficiency and faster responses. When the chain is
set up, cntlm should be used as a proxy in your applications. Cntlm also
integrates transparent TCP/IP port forwarding (tunneling) through the parent
(incl. authentication).
WWW: http://cntlm.sourceforge.net/
PR: ports/137016
Submitted by: Antony Mawer <ports at mawer.org>
