5fc769f6b1
Previously if `sysctl_set=no` (which is the default) this module only checked for changes in the sysctl.conf file to decide whether it should reload it or not. This means that if the values in the conf file are the same as they are set with the module, but the current values on the system are different, that this module wouldn't apply the changes on the system and thus the value set with the module wouldn't be applied on the OS. This isn't obvious and it doesn't make sense that the module works like that by default, especially because there is a separate option `reload`. Now sysctl will also check if the current value differs on the system and if it does, it will reload the file again. |
||
|---|---|---|
| .. | ||
| host_vars | ||
| targets | ||
| cloud-config-aws.ini.template | ||
| cloud-config-azure.ini.template | ||
| cloud-config-cloudscale.ini.template | ||
| cloud-config-cs.ini.template | ||
| cloud-config-gcp.ini.template | ||
| cloud-config-hcloud.ini.template | ||
| cloud-config-opennebula.ini.template | ||
| cloud-config-openshift.kubeconfig.template | ||
| cloud-config-scaleway.ini.template | ||
| cloud-config-tower.ini.template | ||
| cloud-config-vcenter.ini.template | ||
| cloud-config-vultr.ini.template | ||
| integration.cfg | ||
| integration_config.yml | ||
| inventory | ||
| inventory.networking.template | ||
| inventory.remote.template | ||
| inventory.winrm.template | ||
| network-integration.cfg | ||
| target-prefixes.network | ||
| windows-integration.cfg | ||