Lines Matching full:scripts

35  * for passing into further DDB commands.  Certain scripts are run
39  * Scripts may be managed from within DDB using the script, scripts, and
44  * - Allow scripts to be defined using tunables so that they can be defined
45  *   before boot and be present in single-user mode without boot scripts
48  *   statically allocated buffers to hold defined scripts.  However, when
49  *   scripts are being defined from userspace via sysctl, we could in fact be
52  * - When scripts run automatically on entrance to DDB, placing "continue" at
84  * Global list of scripts -- defined scripts have non-empty name fields.
91  * recursion of scripts (one may reference another), we need one buffer for
101  * to validate scripts from within a script.  This is used only in
109  * However, it is required when interacting with scripts from user space
330  * scripts				- lists scripts
338  * List scripts and their contents.
454  * debug.ddb.scripting.scripts     - List of names *and* scripts
496 SYSCTL_PROC(_debug_ddb_scripting, OID_AUTO, scripts,
499     "List of defined scripts");