MAXDAEM parameter: Difference between revisions
Jump to navigation
Jump to search
m (minor formatting) |
(Indicated minimum value of 10 for RKTools) |
||
| Line 9: | Line 9: | ||
<dd>User 0 CCAIN parameters | <dd>User 0 CCAIN parameters | ||
<dt>Related products | <dt>Related products | ||
<dd>All | <dd>All. | ||
<p><b>NOTE:</b> If using any of the RKTools such as SIRMON, SIRSCAN, SIRPRO etc., the minimum required is MAXDAEM=10.</p> | |||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">[[Sirius Mods]]</var> Version 6.7 | <dd><var class="product">[[Sirius Mods]]</var> Version 6.7 | ||
Revision as of 21:43, 21 November 2017
Maximum Daemon objects per user
Summary
- Default value
- 1
- Parameter type
- System
- Where set
- User 0 CCAIN parameters
- Related products
- All.
NOTE: If using any of the RKTools such as SIRMON, SIRSCAN, SIRPRO etc., the minimum required is MAXDAEM=10.
- Introduced
- Sirius Mods Version 6.7
Description
This parameter indicates the maximum number of sdaemon threads that can be used by an individual thread. Such threads are allocated by New method for Daemon objects; or by a number of the (deprecated) Sirius $functions such as: $CommBg, $Command or $CommndL.
Since sdaemon threads are a relatively scarce resource, it is not a good idea for a thread to use more than a handful of them at a time. Unfortunately, with Daemon objects, especially such objects embedded in another class, it is possible for a single runaway request to cause great problems by quickly consuming every daemon thread in an Online.