Re: [mosquitto-dev] Fwd: Reload configuration in Windows

[Mikkel Kirkgaard Nielsen <miki@xxxxxxxxx>]

Hi Spiros.

Generally a signalled reload would bring the period in which the service is unavailable to a minimum. A reload would also be able to keep unaffected existing connections to bridged brokers and clients open, while performing only the necessary actions to reinitialise internal configuration structures. That is also  what I see happening on inspecting the reload handler at https://github.com/eclipse/mosquitto/blob/master/src/loop.c#L390. Note that not all configuration options are handled during  reloading, see notes in man page about each.

A full stop/start of the broker would definitely cause all connections to be closed but to my knowledge not cause any additional data loss if you have persistence enabled.

It apears like there is a feature coming up in 1.5 using a mechanism in Windows called named events. A patch has been merged in the develop branch, take a look at https:/github.com/eclipse/mosquitto/pull/163.

For the advanced user a recompile of the current mosquitto in cygwin would probably make it able to handle posix signals (https://www.cygwin.com/cygwin-ug-net/highlights.html#signal).

Regards,
Mikkel

On 24 May 2017 15:34:45 CEST, Spiros Apostolou <s.st.apostolou@xxxxxxxxx> wrote:

Any thoughts on this?

---------- Forwarded message ----------
From: Spiros Apostolou <s.st.apostolou@xxxxxxxxx>
Date: Thu, May 11, 2017 at 10:28 AM
Subject: Reload configuration in Windows
To: mosquitto-dev@xxxxxxxxxxx

Is there a way to reload the configuration file without restarting the service in Windows? 

I'm assuming that restarting the service may cause unexpected behavior whilst sending a signal (in Linux) probably does some better handling and does not result in anything unwanted. 

If that's not the case should I simply restart the service? 

Thanks

Spiros

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.