MSIR.0826 NONPRE doesn't make sense for DISALLOW: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
mNo edit summary |
||
Line 1: | Line 1: | ||
A <var>SIRMETH DISALLOW</var> command was issued with a < | A <var>[[SIRMETH command|SIRMETH DISALLOW]]</var> command was issued with a <var>NONPRE</var> qualifier on a subsystem name. Since non-pre-compiled requests in a subsystem have no privileges to set globals, it doesn't make sense to disallow it. | ||
If the intent was to remove privileges granted to non-pre-compiled requests via a previous <var>SIRMETH ALLOW</var> command, the <var>SIRMETH ALLOW</var> command should be re-issued without the <var>NONPRE</var> keyword, or a <var>SIRMETH ALLOW</var> command should be issued without the <var>NONPRE</var> keyword for the subset of the subsystems for which privileges are to be removed from non-pre-compiled requests. | |||
[[Category:Sirius Mods messages]] | [[Category:Sirius Mods messages]] |
Revision as of 19:51, 23 April 2014
A SIRMETH DISALLOW command was issued with a NONPRE qualifier on a subsystem name. Since non-pre-compiled requests in a subsystem have no privileges to set globals, it doesn't make sense to disallow it.
If the intent was to remove privileges granted to non-pre-compiled requests via a previous SIRMETH ALLOW command, the SIRMETH ALLOW command should be re-issued without the NONPRE keyword, or a SIRMETH ALLOW command should be issued without the NONPRE keyword for the subset of the subsystems for which privileges are to be removed from non-pre-compiled requests.