BUMP command: Difference between revisions
m (Created page with "'''BUMP user_num''' This operator command requests that the equivalent of the Model 204 BUMP command be issued against the indicated user number. This command is useful if a...") |
m (Created page with "'''BUMP user_num''' This operator command requests that the equivalent of the Model 204 BUMP command be issued against the indicated user number. This command is useful if a...") |
||
| Line 1: | Line 1: | ||
'''BUMP user_num''' | '''BUMP user_num''' | ||
This operator command requests that the equivalent of the [[Model 204]] BUMP command be issued against the indicated user number. This command is useful if a high priority user is looping in an Online, making it impossible for anyone else to do anything. | This operator command requests that the equivalent of the [[Model 204]] <var>BUMP command</var> be issued against the indicated user number. This command is useful if a high priority user is looping in an Online, making it impossible for anyone else to do anything. | ||
To | To “bump” user number 18, for example. issue the command: | ||
BUMP 18 | BUMP 18 | ||
Unlike the ''Model 204'' BUMP command, the operator BUMP command only accepts a single user number, and it does not accept userids or file names. To determine the user number of the running user, issue the [[MONITOR command]]. It is recommended that the MONITOR command be issued several times to ensure that a single user is indeed looping and that the performance problem is not simply the result of excess demand. | Unlike the ''Model 204'' <var>BUMP command</var>, the operator <var>BUMP command</var> only accepts a single user number, and it does not accept userids or file names. To determine the user number of the running user, issue the [[MONITOR command]]. It is recommended that the MONITOR command be issued several times to ensure that a single user is indeed looping and that the performance problem is not simply the result of excess demand. | ||
If a loop situation is caused by a ''Model 204'' bug, it is possible that a BUMP command will fail to force the looping user off the system. In this case, it might be necessary to issue the [[RESTART Command|RESTART command]] to break the loop. | If a loop situation is caused by a ''Model 204'' bug, it is possible that a <var>BUMP command</var> will fail to force the looping user off the system. In this case, it might be necessary to issue the [[RESTART Command|RESTART command]] to break the loop. | ||
[[Category:Operator commands]] | [[Category:Operator commands]] | ||
Revision as of 20:00, 27 June 2011
BUMP user_num
This operator command requests that the equivalent of the Model 204 BUMP command be issued against the indicated user number. This command is useful if a high priority user is looping in an Online, making it impossible for anyone else to do anything.
To “bump” user number 18, for example. issue the command:
BUMP 18
Unlike the Model 204 BUMP command, the operator BUMP command only accepts a single user number, and it does not accept userids or file names. To determine the user number of the running user, issue the MONITOR command. It is recommended that the MONITOR command be issued several times to ensure that a single user is indeed looping and that the performance problem is not simply the result of excess demand.
If a loop situation is caused by a Model 204 bug, it is possible that a BUMP command will fail to force the looping user off the system. In this case, it might be necessary to issue the RESTART command to break the loop.