RCTL.CONF(5) BSD File Formats Manual RCTL.CONF(5)NAME
rctl.conf -- resource limits database defaults
DESCRIPTION
The /etc/rctl.conf file is read in when the system goes into multi-user mode to set default contents of the RCTL database. The
/etc/rctl.conf is in the format of the rctl(8) command, i.e.
subject:subject-id:resource:action=amount/per
Comments are denoted by a ``#'' at the beginning of a line. Comments can also exist at the end of a line, as seen in the EXAMPLES section,
below.
FILES
/etc/rctl.conf Initial settings for rctl(8).
EXAMPLES
To limit the number of processes for users in login class "testing", use a rule like
# Resource limits for the "testing" class.
loginclass:testing:nproc:deny=100/user # At most 100 processes per user
SEE ALSO rctl(8)HISTORY
The rctl.conf file appeared in FreeBSD 9.0.
BSD April 14, 2011 BSD
Check Out this Related Man Page
rctladm(1M)rctladm(1M)NAME
rctladm - display or modify global state of system resource controls
SYNOPSIS
rctladm [-lu] [-e action] [-d action] [name...]
The rctladm command allows the examination and modification of active resource controls on the running system. An instance of a resource
control is referred to as an rctl. See setrctl(2) for a description of an rctl; see resource_controls(5) for a list of the rctls supported
in the current release of the Solaris operating system. Logging of rctl violations can be activated or deactivated system-wide and active
rctls (and their state) can be listed.
The following options are supported:
-d action Disable (-d) or enable (-e) the global action on the specified rctls. If no rctl is specified, no action is taken and an
-e action error status is returned. You can use the special token all with the disable option to deactivate all global actions on a
resource control.
You can set the syslog action to a specific degree by assigning a severity level. To do this, specify syslog=level, where
level is one of the string tokens given as valid severity levels in syslog(3C). You can omit the common LOG_ prefix on the
severity level.
-l List available rctls with event status. This option displays the global event actions available for each rctl and the
action name used with the enable (-e) and disable (-d) options. The global flag values for the control are also displayed.
If one or more name operands are specified, only those rctls matching the given names is displayed.
This is the default action if no options are specified.
-u Configure resource controls based on the contents of /etc/rctladm.conf. Any name operands are ignored.
The following operands are supported:
name The name of the rctl to operate on. Multiple rctl names may be specified. If no names are specified, and the list
action has been specified, then all rctls are listed. If the enable or disable action is specified, one or more
rctl names must be specified.
Example 1: Activating System Logging for Specific Violations
The following command activates system logging of all violations of task.max-lwps.
# rctladm -e syslog task.max-lwps
#
Example 2: Examining the Current Status of a Specific Resource
The following command examines the current status of the task.max-lwps resource.
$ rctladm -l task.max-lwps
task.max-lwps syslog=DEBUG
$
The following exit values are returned:
0 Successful completion.
1 A fatal error occurred. A message is written to standard error to indicate each resource control for which the operation failed.
The operation was successful for any other resource controls specified as operands.
2 Invalid command line options were specified.
/etc/rctladm.conf Each time rctladm is executed, it updates the contents of rctladm.conf with the current configuration.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWesu |
+-----------------------------+-----------------------------+
setrctl(2), getrctl(2), prctl(1), rctlblk_get_global_flags(3C), rctlblk_get_global_action(3C), attributes(5), resource_controls(5)
By default, there is no global logging of rctl violations.
1 Oct 2004 rctladm(1M)