Cumulus Support

Mark,

Is it by design that b3214 defaults to Data Logging enabled?

Probably a carry over from testing release. Just remove the ticks in Data and Debug logging and Save.

Yes, but every restart it has the logging on so it is released as a beta or alike.
Better to rerelease one with the logging default off.

Oh come on Hans how many times do you have to restart Mx, once in a blue moon!! Hardly a good reason for a new release.

water01 wrote: ↑Sat 05 Nov 2022 4:09 pm Oh come on Hans how many times do you have to restart Mx, once in a blue moon!! Hardly a good reason for a new release.

CMX restarts daily because at 9h00 I make a backup and during the backup I don't want to have CMX running.
The result is that I have huge logfiles because, as you may imagine, this is a completely automatic thing.

Sorry, I have switched to a new build computer, and it was copying the debug build rather than the release build to the zip.

I have updated the zip file to CumulusDist3214a.zip. It is exactly the same as the last version except this time with the release executable.

Thanks

Just as an FYI - I'm not in a huge hurry to build a docker container for this change immediately but it will be updated soon (in the next few days)

water01 wrote: ↑Sat 05 Nov 2022 4:09 pm Oh come on Hans how many times do you have to restart Mx, once in a blue moon!! Hardly a good reason for a new release.

Also some of us restart CMX on a regular basis to overcome the memory leak(s) in mono. I have three instances running on a Pi4 and restart them every week.

philpugh wrote: ↑Sun 06 Nov 2022 12:51 pm

water01 wrote: ↑Sat 05 Nov 2022 4:09 pm Oh come on Hans how many times do you have to restart Mx, once in a blue moon!! Hardly a good reason for a new release.

Also some of us restart CMX on a regular basis to overcome the memory leak(s) in mono. I have three instances running on a Pi4 and restart them every week.

I also use Mono but never experience the memory leak. I only restart on upgrade, or if the host has had an upgraded kernel.

The memory leak only seems to affect network-based stations.

mcrossley wrote: ↑Sun 06 Nov 2022 4:11 pm The memory leak only seems to affect network-based stations.

Oh yes, I remember you stating that before