Tobias Assarsson

This seems to work for me... ``` healthcheck: test: ["CMD", "mosquitto_sub", "-t", "$$SYS/#", "-C", "1", "-i", "healthcheck", "-W", "3"] interval: 30s timeout: 10s retries: 5 start_period: 20s ```

note that `$$` in bash results in the current shells pid... `echo mosquitto_sub -t $$SYS/# -C 1 -i healthcheck1 -W 3` => `mosquitto_sub -t 107926SYS/# -C 1 -i healthcheck1 -W...

* `-t '$SYS/#'` topic to subscribe to * `-C 1` receive one message and exit * `-i healthcheck` set client-id to "healthcheck" * `-W 3` timeout after 3 seconds if...

I'm not sure if this is the same issue, but there is a fix in 2.0.13 touching the area: `Fix max_keepalive option not being able to be set to 0.`...

problem is, a keepalive value of 0 is technically longer than any other number because it turns the functionality off. Let's assume you want a maximum keep alive of 60...

May be. I don't know the exact details to why it was done this way. Perhaps to avoid too much confusion in the config docs when the default suddenly change...

I think you are supposed to just use `mosquitto.h`, `mosquitto_plugin.h` and perhaps the `mosquitto_broker.h`. It contains both definitions of callbacks and module functions to get what you are looking for,...

What was it that you needed, that you couldn't find in those 3 headers? FFI will always be a great deal of boilerplate and naturally be either plugins or c...

is that the whole configuration? ``` listener 9001 127.0.0.1 protocol websockets ```

running this tiny config in a container for 2.0.11 has the same issue. 2.0.12 does not. not sure if this is a libwebsockets or mosquitto issue, but you could try...