SIRMETH command: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 15: | Line 15: | ||
<p class="syntax">SIRMETH {ALLOW | DISALLOW} - | <p class="syntax">SIRMETH {ALLOW | DISALLOW} - | ||
{SYSTEMSET | SUBSYSTEMSET | - | {SYSTEMSET | SUBSYSTEMSET | - | ||
SUBSYSTEMCONTEXT csubsys | ALL} - | SUBSYSTEMCONTEXT <span class="term">csubsys</span> | ALL} - | ||
[SUBSYSTEM subsys [NONPRE] ] </p> | [SUBSYSTEM <span class="term">subsys</span> [NONPRE] ] </p> | ||
For more information about the <var>SIRMETH</var> command, see [[System and Subsystem classes#Using SIRMETH to specify security rules| | For more information about the <var>SIRMETH</var> command, see [[System and Subsystem classes#Using SIRMETH to specify security rules|Using SIRMETH to specify security rules]]. | ||
<!-- SPY - OWNED BY ITS --> | <!-- SPY - OWNED BY ITS --> | ||
Latest revision as of 19:45, 23 April 2014
Note: This is a Sirius Mods-only command prior to Version 7.5 of Model 204.
The SIRMETH command provides system managers with the ability to allow specific subsystems or even all users, whether or not they are system managers, to do certain things that previously only system managers and pre-compiled subsystem procedures could do. These things are:
- Set system globals and strings.
- Set subsystem globals and strings.
- Set a subsystem context.
SIRMETH command syntax
SIRMETH {ALLOW | DISALLOW} - {SYSTEMSET | SUBSYSTEMSET | - SUBSYSTEMCONTEXT csubsys | ALL} - [SUBSYSTEM subsys [NONPRE] ]
For more information about the SIRMETH command, see Using SIRMETH to specify security rules.