Displaying 2 results from an estimated 2 matches for "andomly".
Did you mean:
randomly
2015 Feb 09
1
Tinc1.1 generates Port automatically when port is occupied
...t; it's not running in an interactive TTY.
>
Yes, that would be an improvement IMO. I must say that *I* do not really
like such differences in behavior much, though. I would personally opt for
making the choice interactive, then ("do you want to (F)orce the generation
of port=655 or (R)andomly pick another available port? F/R: "). Then it is
still super easy to use and very obvious that this qbehavior will not work
in non-interactive scripts. But this is a bit subjective, now I may be
conceived as pedantic :-)
>
> > - it is too clever to be expected. You might not have te...
2015 Feb 02
2
Tinc1.1 generates Port automatically when port is occupied
I like the config generator of tinc 1.1! An issue to consider on the
default behavior:
It turns out 'tinc -n mynet init mynodename' makes up a default Port=...
when the standard port is taken:
"Warning: could not bind to port 655. Tinc will instead listen on port
22911".
It is nice that this is autodetected and warned, but I wonder whether it is
nice to let this