Allow interactive arguments (seconds and intervals) of fb_lock_print to be 32-bit integers [CORE1906] #2337
Labels
affect-version: 1.5.4
affect-version: 1.5.5
affect-version: 1.5.6
affect-version: 2.0.0
affect-version: 2.0.1
affect-version: 2.0.2
affect-version: 2.0.3
affect-version: 2.0.4
affect-version: 2.0.5
affect-version: 2.1.0
affect-version: 2.1.1
affect-version: 2.1.2
affect-version: 2.1.3
affect-version: 2.5 Alpha 1
affect-version: 2.5 Beta 1
affect-version: 2.5 Beta 2
affect-version: 3.0 Initial
component: lock_print
fix-version: 3.0 Alpha 1
priority: trivial
type: improvement
Submitted by: Steve Friedl (sjfriedl)
fb_lock_print -ia takes two numeric parameters - a number of seconds per interval, and a number of intervals, so one can do "fb_lock_print -ia 1 60" to see the lock stats every second for a minute. But the number-of-intervals is internally a SSHORT, and it's limited to 32767 for no particularly good reason.
By using an /int/ instead of a /short/, it fits the natural return value of atoi(), and I can't see any downside for this. The variable and parameter to the affected function are strictly internal, so this has no impact on any API anywhere.
Commits: abd3a32
The text was updated successfully, but these errors were encountered: