On 21/09/15 12:55, Martin Lucina wrote:
On Tuesday, 08.09.2015 at 23:11, Antti Kantee wrote:
Hi,
I (finally!) disabled default sysproxy on TCP port 12345 for Rumprun. If you
want the same now, you can specify on the rumprun tool command line "-e
RUMPRUN_SYSPROXY=tcp://0:12345". That of course works only when you have
sysproxy in your bake config.
Why use an environment variable rather than a switch to rumprun?
It is an existing mechanism which can be used without a) having to
ponder the deeper meanings of new mechanisms b) having to add new code
c) causing a feature regression d) having to risk signing on to support
an potentially inconvenient interface for backward compatibility.
In other words, the goal was to turn off default sysproxy without "c".
The paragraph below was meant as a not-so-subtle hint that e.g. a switch
could be a more appropriate mechanism if sufficiently analyzed and chewed.
Ideally, one should be able to specify multiple sysproxy listeners on the
command line, e.g. if one wants to listen both on tcp and tcp6. That's not
straightforward to do with an environment variable, but we could always add
a switch to rumprun (e.g. -S). config.json would then have an array of
strings as the sysproxy listeners. Yes/no?
