ldmud-3.3.719/
ldmud-3.3.719/doc/
ldmud-3.3.719/doc/efun.de/
ldmud-3.3.719/doc/efun/
ldmud-3.3.719/doc/man/
ldmud-3.3.719/doc/other/
ldmud-3.3.719/mud/
ldmud-3.3.719/mud/heaven7/
ldmud-3.3.719/mud/lp-245/
ldmud-3.3.719/mud/lp-245/banish/
ldmud-3.3.719/mud/lp-245/doc/
ldmud-3.3.719/mud/lp-245/doc/examples/
ldmud-3.3.719/mud/lp-245/doc/sefun/
ldmud-3.3.719/mud/lp-245/log/
ldmud-3.3.719/mud/lp-245/obj/Go/
ldmud-3.3.719/mud/lp-245/players/lars/
ldmud-3.3.719/mud/lp-245/room/death/
ldmud-3.3.719/mud/lp-245/room/maze1/
ldmud-3.3.719/mud/lp-245/room/sub/
ldmud-3.3.719/mud/lp-245/secure/
ldmud-3.3.719/mud/sticklib/
ldmud-3.3.719/mud/sticklib/src/
ldmud-3.3.719/mudlib/deprecated/
ldmud-3.3.719/mudlib/uni-crasher/
ldmud-3.3.719/pkg/
ldmud-3.3.719/pkg/debugger/
ldmud-3.3.719/pkg/diff/
ldmud-3.3.719/pkg/misc/
ldmud-3.3.719/src/
ldmud-3.3.719/src/autoconf/
ldmud-3.3.719/src/ptmalloc/
ldmud-3.3.719/src/util/
ldmud-3.3.719/src/util/erq/
ldmud-3.3.719/src/util/indent/hosts/next/
ldmud-3.3.719/src/util/xerq/
ldmud-3.3.719/src/util/xerq/lpc/
ldmud-3.3.719/src/util/xerq/lpc/www/
ldmud-3.3.719/test/generic/
ldmud-3.3.719/test/inc/
ldmud-3.3.719/test/t-0000398/
ldmud-3.3.719/test/t-0000548/
ldmud-3.3.719/test/t-030925/
ldmud-3.3.719/test/t-040413/
ldmud-3.3.719/test/t-041124/
ldmud-3.3.719/test/t-language/
SYNOPSIS
        #include <sys/rtlimits.h>

        void set_limits(int tag, int value, ...)
        void set_limits(int * limits)

DESCRIPTION
        Set the default runtime limits from the given arguments. The new
        limits will be in effect as the initial 'max limits' with the
        next execution thread.

        The arguments can be given in two ways: as an array (like the one
        returned from query_limits(), or as a list of tagged values.
        The limit settings recognize three special values:

            LIMIT_UNLIMITED: the limit is deactivated
            LIMIT_KEEP:      the former setting is kept
            LIMIT_DEFAULT:   the 'global' default setting is used.

        For LIMIT_COST, the special values have these meaning:
            LIMIT_UNLIMITED: at maximum 1 tick is accounted
            LIMIT_KEEP:      LIMIT_COST is set to 0
            LIMIT_DEFAULT:   LIMIT_COST is set to -100

        The efun causes a privilege violation ("set_limits", current_object,
        limits-array).

EXAMPLES
        set_limits( ({ 200000 }) )
        set_limits( LIMIT_EVAL, 200000 )
          --> set new default eval_cost limit to 200000

        set_limits( ({ LIMIT_UNLIMITED, LIMIT_KEEP, 5000 }) )
        set_limits( LIMIT_EVAL, LIMIT_UNLIMITED, LIMIT_ARRAY, LIMIT_KEEP,
                    LIMIT_MAPPING, 5000 )
          --> set new eval_cost limit to unlimited, keep the current
              array size limit, and limit mapping sizes to 5000.

HISTORY
        Introduced in LDMud 3.2.7.
        LDMud 3.3.563 introduced LIMIT_COST.
        LDMud 3.3.677 introduced LIMIT_MAPPING_KEYS, LIMIT_MAPPING_SIZE.

SEE ALSO
        limited(E), query_limits(E)