Example of Workload Manager assignment rules
This example shows a top-level rules file for the configuration Config (/etc/wlm/Config/rules file).
* This file contains the rules used by WLM to
* assign a process to a superclass
*
* class resvd user group application type tag
db1 - - - /usr/bin/oracle* _DB1
db2 - - - /usr/bin/oracle* _DB2
devlt - - dev - - -
VPs - bob,ted - - - -
acctg - - acct* - - -
System - root - - - -
Default - - - - - -The following is an example of the rules file for the devlt superclass in the /etc/wlm/Config/devlt/rules file:
* This file contains the rules used by WLM to
* assign a process to a subclass of the
* superclass devlt
*
* class resvd user group application type tag
hackers - jim,liz - - - -
hogs - - - - 64bit+plock -
editors - !sue - /bin/vi,/bin/emacs - -
build - - - /bin/make,/bin/cc - -
Default - - - - - -Note: The asterisk (*) is the comment character used in
the rules file.
The following are examples using this rules file. The
following examples assume that the superclasses and subclasses described
do not have the inheritance attribute set to yes. If inheritance were
enabled, new processes would inherit the superclass or subclass from
their parent processes.
- If user joe from group acct3 executes /bin/vi, then the process will be put in superclass acctg.
- If user sue from group dev executes /bin/emacs, then the process will be put in the superclass devlt (group ID match), but will not be classified into the editors subclass, because the user is excluded from that class. The process will go to devlt by default.
- When a database administrator with a user ID of oracle and a group ID of dbm starts /usr/sbin/oracle to serve the DB1 database, the process will be classified in the Default superclass. Only when the process sets its tag to _DB1 will it be assigned to the superclass db1.