-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
New value for 'socket' config does not create file, default value keep being used #8305
Comments
Hey @filiagees, this is not a bug; In the past this was not enforced (incorrectly), while from 5.4.0 and on this has been changed. |
@Smjert thanks for such a fast reply, You are right, when I set On the other hand, running a ¹details (click to expand)Configadded to 'config' block, in /etc/osquery/osquery.conf:
cat /etc/osquery/osquery.flags:
Result:
If you think it's neither a bug nor a doc issue, I will close this issue. |
The default value is correct, it's whatever it's set to when you don't pass that flag (which is hardcoded), but the value it shows it's indeed wrong. |
Bug report
What operating system and version are you using?
What version of osquery are you using?
What steps did you take to reproduce the issue?
"socket": "/tmp/osqueryd.sock.em"
, inside "config" block, in file/etc/osquery/osquery.conf
service osqueryd restart
osqueryi "SELECT * FROM osquery_flags where name = 'extensions_socket';"
file /var/osquery/osquery.em /tmp/osqueryd.sock.em
What did you expect to see?
I expect to see the file of "default_value" column as not present in filesystem; and the file in "value" column as a socket. eg:
What did you see instead?
I see the opposite: the "default_value" as a socket file, and nothing is created with the new config.
The text was updated successfully, but these errors were encountered: