-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
detangle: Move osquery shutdown logic outside of Initializer #6530
Conversation
The goal is to have less inter-dependency within osquery components. This is the first of several changes that take small steps towards a simpler dependency graph. Later we can revisit the directory structure to see if we can convey what components are intended to be widely used and what components are specialized.
9222a29
to
5c24bc5
Compare
|
c5981aa
to
9606071
Compare
e626a28
to
1f3e2f2
Compare
c4b6c46
to
29ef8fd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I looked over this (up to 29ef8fd), but I don't feel super comfortable with this part of the code. From what I can tell, it looks cleaner. I don't know if anyone else will take a look, but I can thumb this if no one else steps up
* @param retcode the request return code for the process. | ||
* @param system_log A log line to write to the system's log. | ||
*/ | ||
void requestShutdown(int retcode, const std::string& system_log); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think it makes sense to name this forceShutdown
instead of just having the extra system_log
argument?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe, but for this PR the thesis is detangling. We can refactor/rename things as separate as separate thesis later.
The goal is to have less inter-dependency within osquery components.
This is the first of several changes that take small steps towards a
simpler dependency graph.
Later we can revisit the directory structure to see if we can convey
what components are intended to be widely used and what components
are specialized.
See #5990.