.. _vol.action.service_and_volume_object_actions.pg_freeze: :cmd:`om vol pg freeze` ----------------------- Freeze the tasks of a process group. :opt:`--color=` +++++++++++++++++++++++ Colorize output. Possible values are: * auto: guess based on tty presence * always|yes: always colorize * never|no: never colorize :opt:`--daemon` +++++++++++++++ A flag inhibiting the command daemonization. Set by the daemonization routine. :opt:`--debug` ++++++++++++++ Increase stream and file log verbosity up to the debug level. :opt:`--dry-run` ++++++++++++++++ Show the action execution plan. :opt:`--env` ++++++++++++ Export the uppercased variable in the os environment. With the create action only, set a env section parameter in the service configuration file. Multiple ``--env =`` can be specified. For all other actions. :opt:`--local` ++++++++++++++ Execute the service action on the local service instances only, ignoring cluster-wide considerations. :opt:`--master` +++++++++++++++ Limit the action scope to the master service resources. :opt:`--namespace=` +++++++++++++++++++++++++++ The namespace to switch to for the action. Namespaces are cluster partitions. A default namespace can be set for the session setting the OSVC_NAMESPACE environment variable. :opt:`--node=` ++++++++++++++++++++++ The node to send a request to. If not specified the local node is targeted. :opt:`--nolock` +++++++++++++++ Don't acquire the action lock. Dangerous, but can be useful to set parameters from an action trigger. :opt:`--rid=` +++++++++++++++++++++ A resource specifier expression like ``[,]``, where ```` can be: * A resource id * A driver group name (app, fs, disk, ...) Examples: * ``app`` all app resources * ``container#1,ip#1`` only container#1 and ip#1 :opt:`--slave=` +++++++++++++++++++++++ Limit the action to the service resources in the specified, comma-separated, slaves. :opt:`--slaves` +++++++++++++++ Limit the action scope to service resources in all slaves. :opt:`--status=` ++++++++++++++++++++++++ Operate only on service with a local instance in the specified availability status (up, down, warn, ...). :opt:`--subsets=` +++++++++++++++++++++++++ Limit the action to the resources in the specified, comma-separated, list of subsets. :opt:`--tags=` ++++++++++++++++++++++ A comma-separated list of resource tags to limit action to. The ``+`` separator can be used to impose multiple tag conditions. For example, ``tag1+tag2,tag3`` limits the action to resources with both tag1 and tag2, or tag3. :opt:`--waitlock=` ++++++++++++++++++++++++++ A duration expression like ``5s``. The maximum wait time when acquiring the service action lock. :opt:`-f, --force` ++++++++++++++++++ Force action, ignore sanity checks. :opt:`-h, --help` +++++++++++++++++ Show this help message and exit. :opt:`-p, --parallel` +++++++++++++++++++++ Start actions on specified services in parallel. :kw:`max_parallel` in node.conf limits the number of parallel running subprocesses. :opt:`-s, VAL, --service=` ++++++++++++++++++++++++++++++++++ A service selector expression ``[!][[!]]`` where: - ``!`` is the expression negation operator - ```` can be: - ``,`` OR expressions - ``+`` AND expressions - ```` can be: - a shell glob on service names - ```` where: - ```` can be: - ``:`` - ``:`` - ``.`` - ``.`` - `` dictionary extended under the 'nodes' key by each instance 'status' and 'config' data>`` - ```` can be: - ``<`` ``>`` ``<=`` ``>=`` ``=`` - ``~`` the string or any list element matches the regexp value - ``~=`` the string matches regexp value or any list element is the value Examples: - ``*dns,ha*+app.timeout>1`` - ``ip:+task:`` - ``!*excluded`` - ``$.avail=warn`` - ``$.nodes.*.status.avail=warn`` Note: - ``!`` usage requires single quoting the expression to prevent shell history expansion