Use Monit to auto restart if CPU usage high in Native OSX strategy

[ricmatsui]

• Fixes High CPU usage and syncing stops with native OSX when files are being created and removed #497
• Issue has repro steps
• Adding monit to Native OSX image done here: Updated binutils version 2.33.1-r0 to 2.34-r0. docker-image-unison#11
• This PR adds ability to control three configuration options from the config file

---

• monit_enable - Control if monit is used, default false
• monit_interval - How often in seconds monit performs check, default 5
• monit_high_cpu_cycles - How many cycles of monit checks need to have high cpu usage (>50%) to trigger a restart, default 2

[EugenMayer]

@ricmatsui great contribution, thats really awesome! Could you please update the docs also, that means

https://github.com/EugenMayer/docker-sync/wiki/2.-Configuration
and in parallel https://github.com/EugenMayer/docker-sync/blob/master/example/docker-sync.yml

It would be great to have one monit example in the boilerplate, what do you think? https://github.com/EugenMayer/docker-sync-boilerplate

I also would like to have a advanced topic on https://github.com/EugenMayer/docker-sync/wiki about that - i created https://github.com/EugenMayer/docker-sync/wiki/native_OSX-advanced---monitoring

Could you write some lines about why this is useful, what it does and link to the configuration? That would be awesome.

[ricmatsui]

@EugenMayer Thanks, I have added the docs now in those locations and here's an example, too: EugenMayer/docker-sync-boilerplate#11

[EugenMayer]

great, that's really well done. last topic to discuss is the default, right now it's on. I would suggest not doing that for now, or we would be forced to release a new minor... that would delay that feature. in addition we do not have a wide field test yet and we do not really now which cycles are a sane 'mass compatibile' value, with possible tradeoffs on reaction time but for all (anybody can adjust those for quicker reaction and faster cleanup). I pledge for not being on by default for the 0.5.x series, but becoming on by default with 0.6

what are your thoughts on this gentleman?

[ricmatsui]

@EugenMayer Yeah that makes sense, it'll be good to get wider testing sooner. I have switched to off by default in the PRs and docs now!

[EugenMayer]

that's great, this is a long awaited addition to docker-sync, thank you for working your way through that!

I will release this in the next few days with 0.5.3 - any concerns?

[ricmatsuitile]

@EugenMayer No problem, thanks for pushing this out! Sounds great.