Prepratory work for providing more filtering of the output dump.
This makes _no_ difference to the current behaviour, but makes it much
simpler for people who "need", for whatever reason, to hack some private
changes into the db_dump tool.
Signed-off-by: Karl Palsson <karlp@etactica.com>
Limiting queued message depth purely based on message count is hard to
control for memory constrained devices. The size of messages can vary
wildly, from a few bytes, to a few kilobytes. Support a new
max_queued_bytes option, and drop packets when the first limit is
reached. Option defaults to 0 (disabled) by default.
Support also a max_inflight_bytes variable, with similar behaviour.
Fixes (partof) https://github.com/eclipse/mosquitto/issues/100
This pulls up some helper routines for calculating whether to allow
inflight or queuing, resolving some inconsistences in connection
resumption.
Signed-off-by: Karl Palsson <karlp@etactica.com>
This publishes initial 0 figures for all load averages, as is done for
all the existing counter values in the SYS tree. This makes the
behaviour of certain variables use for diagnostics (stored count for
instance) more predictable, instead of changing due to the creation of
load topics as soon as the load became non-zero.
Signed-off-by: Karl Palsson <karlp@etactica.com>
Instead of simply tracking the count of stored messages, keep track of
the total byte size of stored messages. While only informational at
this point, it provides the basis for byte based limits in the future.
Signed-off-by: Karl Palsson <karlp@etactica.com>
A lot of function renaming was done in 663d50a016,
and this websockets patch was merged afterwards. Autobuild testing
doesn't have websockets enabled, and missed this.
Fixes: d9142c3974
Signed-off-by: Karl Palsson <karlp@etactica.com>
mosqPID_shutdown
mosqPID_reload
mosqPID_backup
mosqPID_vacuum
where PID is the PID of the mosquitto process
Signed-off-by: Dmitry Kaukov <dkaukov@opentable.com>