]> git.ipfire.org Git - thirdparty/bacula.git/commit
Fix #5853 about the incorrect behavior of the "status schedule" limit parameter
authorEric Bollengier <eric@baculasystems.com>
Fri, 10 Jan 2020 08:35:41 +0000 (09:35 +0100)
committerKern Sibbald <kern@sibbald.com>
Fri, 31 Jan 2020 13:58:20 +0000 (14:58 +0100)
commitb0566ea6d80183b9c0950d0ee0d850b74abd76a5
tree0bfdb41ed8a57644ee9019990092a036128d9af6
parenta0d62e42ea9fa2260c1b01f56a1d689e3c06d473
Fix #5853 about the incorrect behavior of the "status schedule" limit parameter

As the Schedule are analyzed job per job, the limit must be applied only when the entire
list is computed. Else, we see only the first jobs.
bacula/src/dird/ua_status.c