Details
-
Type:
Bug
-
Status: Unconfirmed
-
Priority:
(None)
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: cf-execd
-
Labels:None
Description
I noticed that when I restart cfengine with a promise, reports from that execution are not sent.
For me this is just a minor annoyance, but if I relied on reports to be reliably sent this could be a problem.
This would be less problematic if cf-execd reloaded itself on control change https://cfengine.com/dev/issues/1885
but there are other situations where reports on restart would be useful. Upgrades and working around memory leaks come to mind.
Here is the policy that I used when I noticed the issue.
<pre>
commands:
February.Day21::
"/etc/init.d/cfengine3"
comment => "Restart cf-execd so that it picks up new splay time setting",
args => "restart",
classes => if_ok("cfengine_restarted"),
action => if_elapsed_day; # This will keep it from happening again,
- unless someone runs without locks
reports:
cfengine_restarted::
"I restarted cfengine, cf-execd should have its new splay time active";
</pre>