Displaying 1 result from an estimated 1 matches for "30s1m".
Did you mean:
3071m
2020 May 28
5
[Bug 3171] New: Error in time conversion
....org
Reporter: ronf at timeheart.net
While experimenting with the RekeyLimit option, I ran across a small
bug in the convtime() function. When I entered a time value of '1m30s',
I found that it converted this to 1860 seconds instead of the expected
90 seconds. Entering it as '30s1m' worked fine as a workaround (as
would just entering "90"), but clearly the conversion is incorrect.
The bug appears to be that the convtime() function doesn't reset the
multiplier back to 1 when it sees the 's'. So, whatever the previous
multiplier was (60 in my example)...