user_ulimit Resource
This page is generated from the Chef Infra Client source code.To suggest a change, edit the user_ulimit.rb file and submit a pull request to the Chef Infra Client repository.
Use the user_ulimit resource to create individual ulimit files that are installed into the /etc/security/limits.d/
directory.
New in Chef Infra Client 16.0.
Syntax
The full syntax for all of the properties that are available to the user_ulimit resource is:
user_ulimit 'name' do
as_hard_limit String, Integer
as_limit String, Integer
as_soft_limit String, Integer
core_hard_limit String, Integer
core_limit String, Integer
core_soft_limit String, Integer
cpu_hard_limit String, Integer
cpu_limit String, Integer
cpu_soft_limit String, Integer
filehandle_hard_limit String, Integer
filehandle_limit String, Integer
filehandle_soft_limit String, Integer
filename String
locks_limit String, Integer
maxlogins_hard_limit String, Integer
maxlogins_limit String, Integer
maxlogins_soft_limit String, Integer
memory_limit String, Integer
msgqueue_hard_limit String, Integer
msgqueue_limit String, Integer
msgqueue_soft_limit String, Integer
process_hard_limit String, Integer
process_limit String, Integer
process_soft_limit String, Integer
rss_hard_limit String, Integer
rss_limit String, Integer
rss_soft_limit String, Integer
rtprio_hard_limit String, Integer
rtprio_limit String, Integer
rtprio_soft_limit String, Integer
sigpending_hard_limit String, Integer
sigpending_limit String, Integer
sigpending_soft_limit String, Integer
stack_hard_limit String, Integer
stack_limit String, Integer
stack_soft_limit String, Integer
username String # default value: 'name' unless specified
virt_limit String, Integer
action Symbol # defaults to :create if not specified
end
where:
user_ulimit
is the resource.name
is the name given to the resource block.action
identifies which steps Chef Infra Client will take to bring the node into the desired state.as_hard_limit
,as_limit
,as_soft_limit
,core_hard_limit
,core_limit
,core_soft_limit
,cpu_hard_limit
,cpu_limit
,cpu_soft_limit
,filehandle_hard_limit
,filehandle_limit
,filehandle_soft_limit
,filename
,locks_limit
,maxlogins_hard_limit
,maxlogins_limit
,maxlogins_soft_limit
,memory_limit
,msgqueue_hard_limit
,msgqueue_limit
,msgqueue_soft_limit
,process_hard_limit
,process_limit
,process_soft_limit
,rss_hard_limit
,rss_limit
,rss_soft_limit
,rtprio_hard_limit
,rtprio_limit
,rtprio_soft_limit
,sigpending_hard_limit
,sigpending_limit
,sigpending_soft_limit
,stack_hard_limit
,stack_limit
,stack_soft_limit
,username
, andvirt_limit
are the properties available to this resource.
Actions
The user_ulimit resource has the following actions:
:create
- Create a ulimit configuration file. (default)
:delete
- Delete an existing ulimit configuration file.
:nothing
- This resource block does not act unless notified by another resource to take action. Once notified, this resource block either runs immediately or is queued up to run at the end of a Chef Infra Client run.
Properties
The user_ulimit resource has the following properties:
as_hard_limit
- Ruby Type: String, Integer
as_limit
- Ruby Type: String, Integer
as_soft_limit
- Ruby Type: String, Integer
core_hard_limit
- Ruby Type: String, Integer
core_limit
- Ruby Type: String, Integer
core_soft_limit
- Ruby Type: String, Integer
cpu_hard_limit
- Ruby Type: String, Integer
cpu_limit
- Ruby Type: String, Integer
cpu_soft_limit
- Ruby Type: String, Integer
filehandle_hard_limit
- Ruby Type: String, Integer
filehandle_limit
- Ruby Type: String, Integer
filehandle_soft_limit
- Ruby Type: String, Integer
filename
- Ruby Type: String | Default Value:
lazy default
locks_limit
- Ruby Type: String, Integer
maxlogins_hard_limit
- Ruby Type: String, Integer
maxlogins_limit
- Ruby Type: String, Integer
maxlogins_soft_limit
- Ruby Type: String, Integer
memory_limit
- Ruby Type: String, Integer
msgqueue_hard_limit
- Ruby Type: String, Integer
msgqueue_limit
- Ruby Type: String, Integer
msgqueue_soft_limit
- Ruby Type: String, Integer
process_hard_limit
- Ruby Type: String, Integer
process_limit
- Ruby Type: String, Integer
process_soft_limit
- Ruby Type: String, Integer
rss_hard_limit
- Ruby Type: String, Integer
rss_limit
- Ruby Type: String, Integer
rss_soft_limit
- Ruby Type: String, Integer
rtprio_hard_limit
- Ruby Type: String, Integer
rtprio_limit
- Ruby Type: String, Integer
rtprio_soft_limit
- Ruby Type: String, Integer
sigpending_hard_limit
- Ruby Type: String, Integer
sigpending_limit
- Ruby Type: String, Integer
sigpending_soft_limit
- Ruby Type: String, Integer
stack_hard_limit
- Ruby Type: String, Integer
stack_limit
- Ruby Type: String, Integer
stack_soft_limit
- Ruby Type: String, Integer
username
- Ruby Type: String | Default Value:
The resource block's name
virt_limit
- Ruby Type: String, Integer
Common Resource Functionality
Chef resources include common properties, notifications, and resource guards.
Common Properties
The following properties are common to every resource:
compile_time
Ruby Type: true, false | Default Value:
false
Control the phase during which the resource is run on the node. Set to true to run while the resource collection is being built (the
compile phase
). Set to false to run while Chef Infra Client is configuring the node (theconverge phase
).ignore_failure
Ruby Type: true, false, :quiet | Default Value:
false
Continue running a recipe if a resource fails for any reason.
:quiet
will not display the full stack trace and the recipe will continue to run if a resource fails.retries
Ruby Type: Integer | Default Value:
0
The number of attempts to catch exceptions and retry the resource.
retry_delay
Ruby Type: Integer | Default Value:
2
The delay in seconds between retry attempts.
sensitive
Ruby Type: true, false | Default Value:
false
Ensure that sensitive resource data is not logged by Chef Infra Client.
Notifications
notifies
Ruby Type: Symbol, 'Chef::Resource[String]'
A resource may notify another resource to take action when its state changes. Specify a
'resource[name]'
, the:action
that resource should take, and then the:timer
for that action. A resource may notify more than one resource; use anotifies
statement for each resource to be notified.If the referenced resource does not exist, an error is raised. In contrast,
subscribes
will not fail if the source resource is not found.
A timer specifies the point during a Chef Infra Client run at which a notification is run. The following timers are available:
:before
Specifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayed
Default. Specifies that a notification should be queued up, and then executed at the end of a Chef Infra Client run.
:immediate
,:immediately
Specifies that a notification should be run immediately, for each resource notified.
The syntax for notifies
is:
notifies :action, 'resource[name]', :timer
subscribes
Ruby Type: Symbol, 'Chef::Resource[String]'
A resource may listen to another resource, and then take action if the
state of the resource being listened to changes. Specify a
'resource[name]'
, the :action
to be taken, and then the :timer
for
that action.
Note that subscribes
does not apply the specified action to the
resource that it listens to - for example:
file '/etc/nginx/ssl/example.crt' do
mode '0600'
owner 'root'
end
service 'nginx' do
subscribes :reload, 'file[/etc/nginx/ssl/example.crt]', :immediately
end
In this case the subscribes
property reloads the nginx
service
whenever its certificate file, located under
/etc/nginx/ssl/example.crt
, is updated. subscribes
does not make any
changes to the certificate file itself, it merely listens for a change
to the file, and executes the :reload
action for its resource (in this
example nginx
) when a change is detected.
If the other resource does not exist, the subscription will not raise an
error. Contrast this with the stricter semantics of notifies
, which
will raise an error if the other resource does not exist.
A timer specifies the point during a Chef Infra Client run at which a notification is run. The following timers are available:
:before
Specifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayed
Default. Specifies that a notification should be queued up, and then executed at the end of a Chef Infra Client run.
:immediate
,:immediately
Specifies that a notification should be run immediately, for each resource notified.
The syntax for subscribes
is:
subscribes :action, 'resource[name]', :timer
Guards
A guard property can be used to evaluate the state of a node during the execution phase of a Chef Infra Client run. Based on the results of this evaluation, a guard property is then used to tell Chef Infra Client if it should continue executing a resource. A guard property accepts either a string value or a Ruby block value:
- A string is executed as a shell command. If the command returns
0
, the guard is applied. If the command returns any other value, then the guard property is not applied. String guards in a powershell_script run Windows PowerShell commands and may returntrue
in addition to0
. - A block is executed as Ruby code that must return either
true
orfalse
. If the block returnstrue
, the guard property is applied. If the block returnsfalse
, the guard property is not applied.
A guard property is useful for ensuring that a resource is idempotent by allowing that resource to test for the desired state as it is being executed, and then if the desired state is present, for Chef Infra Client to do nothing.
PropertiesThe following properties can be used to define a guard that is evaluated during the execution phase of a Chef Infra Client run:
not_if
Prevent a resource from executing when the condition returns
true
.only_if
Allow a resource to execute only if the condition returns
true
.
Examples
The following examples demonstrate various approaches for using the user_ulimit resource in recipes:
Set filehandle limit for the tomcat user:
user_ulimit 'tomcat' do
filehandle_limit 8192
end
Specify a username that differs from the name given to the resource block:
user_ulimit 'Bump filehandle limits for tomcat user' do
username 'tomcat'
filehandle_limit 8192
end
Set filehandle limit for the tomcat user with a non-default filename:
user_ulimit 'tomcat' do
filehandle_limit 8192
filename 'tomcat_filehandle_limits.conf'
end