I have the `service osqueryd stop` hacked in there...
# general
c
I have the
service osqueryd stop
hacked in there, but it's obviously not ideal. I can make it "more chef-like" with a series of
execute
or
service
statements that use notify/inform to chain together, but i'm wondering if the
osqueryctl
needs an exclusive lock on the osquery db to check the syntax of the config file