If you feel you have a bug, please report it on the github issue tracker. There isn't a bot that files bugs from mailing list posts, so this is the best way to make sure it is recorded, and that you also get updates if it is closed.
On Wed, Jan 1, 2014 at 6:25 AM, Walid <[email protected]> wrote: > Its a bug as the decision does not take into account if the change was not > done via the sysctl.conf file > On Dec 31, 2013 6:47 PM, "Walid" <[email protected]> wrote: > >> Hi, >> >> a sysctl task today does not change the state if the sysctl file has the >> kernel configuration item set in RHEL6, e.g. kernel.watchdog disabled, >> however in /proc/sys/kernel/watchdog it is enabled? >> >> - sysctl: name=kernel.watchdog value=0 state=present reload=yes >> >> file /etc/sysctl.conf : kernel.watchdog=0 >> while echo /proc/sys/kernel/watchdog reports back 1 >> running the task reports OK, no change >> >> is that because the sysctl module function is only to update the file, >> but not the system settings? or is that a bug? that if the file conflicts >> with the /proc it does not try to enforce any thing? >> >> regards >> >> Walid >> > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael DeHaan <[email protected]> CTO, AnsibleWorks, Inc. http://www.ansibleworks.com/ -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
