inspec/docs/resources/process.md.erb
David Wrede 9283f19b6e Changing headings to align with SEO best practices
Signed-off-by: David Wrede <dwrede@chef.io>
2016-09-27 12:03:23 -07:00

73 lines
1.6 KiB
Text

---
title: About the processes Resource
---
# processes
Use the `processes` InSpec audit resource to test properties for programs that are running on the system.
## Syntax
A `processes` resource block declares the name of the process to be tested, and then declares one (or more) property/value pairs:
describe processes('process_name') do
its('property_name') { should eq ['property_value'] }
end
where
* `processes('process_name')` must specify the name of a process that is running on the system
* `property_name` may be used to test user (`its('users')`) and state properties (`its('states')`)
## Matchers
This InSpec audit resource has the following matchers:
### be
<%= partial "/shared/matcher_be" %>
### cmp
<%= partial "/shared/matcher_cmp" %>
### eq
<%= partial "/shared/matcher_eq" %>
### include
<%= partial "/shared/matcher_include" %>
### match
<%= partial "/shared/matcher_match" %>
### property_name
The `property_name` matcher tests the named property for the specified value:
its('property_name') { should eq ['property_value'] }
## Examples
The following examples show how to use this InSpec audit resource.
### Test if the list length for the mysqld process is 1
describe processes('mysqld') do
its('list.length') { should eq 1 }
end
### Test if the init process is owned by the root user
describe processes('init') do
its('users') { should eq ['root'] }
end
### Test if a high-priority process is running
describe processes('some_process') do
its('states') { should eq ['R<'] }
end