valitydev/osquery-1
14
0
Fork 0
mirror of https://github.com/valitydev/osquery-1.git synced 2024-11-06 17:45:22 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Small doc fixes (#5186)

Browse Source
This commit is contained in:
ThorodanBrom 2018-09-07 00:12:11 +05:30 committed by Giorgi Guliashvili
parent b485aae9a7
commit 3229743460
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/wiki/deployment/process-auditing.md
View File

@ -90,7 +90,7 @@ There are a few different methods to ensure you have configured auditing correct
4. Verify that your osquery configuration has a query to `SELECT` from the process_events and/or socket_events tables
5. You may also run auditing using osqueryi:
```
$ osqueryi --audit_allow_config=true --audit_allow_sockets=true --audit_persist=true --disable_audit=false
 --events_expiry=1 --events_max=50000 --logger_plugin=filesystem --disable_events=false
$ osqueryi --audit_allow_config=true --audit_allow_sockets=true --audit_persist=true --disable_audit=false --events_expiry=1 --events_max=50000 --logger_plugin=filesystem --disable_events=false
```
If you would like to debug the raw audit events as osqueryd sees them, use the hidden flag `--audit_debug`. This will print all of the RAW audit lines to osquery's stdout.

2
docs/wiki/development/building.md
View File

@ -115,7 +115,7 @@ To speed up the format auditing process please configure your code editor to run
## Dependencies and build internals
The `make deps` command is fairly intense and serves two purposes: (1) to communicate a standard set of environment setup instructions for our build and test nodes, (2) to provide an environment for reproducing errors. The are wonderful auxiliary benefits such as controlling the compiler and compile flags for almost all of our dependencies, controlling security-related features for dependencies, allowing a "mostly" universal build for Linux that makes deployment simple. To read more about the motivation and FAQ for our dependencies environment see the [Github Reference #2253](https://github.com/facebook/osquery/issues/2253).
The `make deps` command is fairly intense and serves two purposes: (1) to communicate a standard set of environment setup instructions for our build and test nodes, (2) to provide an environment for reproducing errors. There are wonderful auxiliary benefits such as controlling the compiler and compile flags for almost all of our dependencies, controlling security-related features for dependencies, allowing a "mostly" universal build for Linux that makes deployment simple. To read more about the motivation and FAQ for our dependencies environment see the [Github Reference #2253](https://github.com/facebook/osquery/issues/2253).
When using `make deps` the environment the resultant binaries will have a minimum set of requirements to run: