Pretty sure if the default is left at 20 it'll affect our CI tests without having the ENV updated there to reduce it.

While I understand wanting to have a more sane default than 2, this would negatively impact new users trying to setup their DMS instance based on our docs with the setup CLI, having to wait up to 20 seconds until the update is actually applied (the CLI will not wait, it updates the monitored config, then defers to check-for-changes.sh). As such it'd also be breaking for any automation reliant upon that existing default (like our CI).

Your main concern would be completely avoided should someone contribute watchexec, which for the majority of users would remove any polling entirely.

The other maintainers may request that this ENV is also handled here:

That's where defaults are usually set (and written to /etc/dms-settings), but since this is specifically for check-for-changes.sh and not likely to be prone to breakage/conflict, I'm not going to require it.

The other maintainers may request that this ENV is also handled here:

docker-mailserver/target/scripts/startup/variables-stack.sh

Lines 50 to 53 in ef66dd5

	# This function sets almost all environment variables. This involves setting
	# a default if no value was provided and writing the variable and its value
	# to the VARS map.
	function __environment_variables_general_setup() {

That's where defaults are usually set (and written to /etc/dms-settings), but since this is specifically for check-for-changes.sh and not likely to be prone to breakage/conflict, I'm not going to require it.

For completeness, please add the new ENV to the list.

Done :)