Lines Matching +full:button +full:- +full:uid
5 .. See scripts/check-sysctl-docs to keep this up to date
13 Documentation/admin-guide/sysctl/index.rst.
15 ------------------------------------------------------------------------------
39 If BSD-style process accounting is enabled these values control
71 The machine hardware name, the same output as ``uname -m``
129 Ctrl-Alt-Delete). Writing a value to this file which doesn't
130 correspond to a running process will result in ``-ESRCH``.
132 See also `ctrl-alt-del`_.
166 %u uid (in initial user namespace)
222 ctrl-alt-del
225 When the value in this file is 0, ctrl-alt-del is trapped and
233 mode, the ctrl-alt-del is intercepted by the program before it
278 See Documentation/driver-api/firmware/fallback-mechanisms.rst.
314 debug information. If enabled, arch-specific all-CPU stack dumping
334 See Documentation/admin-guide/lockup-watchdogs.rst for more information.
346 modern systems rely exclusively on the netlink-based uevent source and
360 1: Will non-maskably interrupt all CPUs and dump their backtraces when
417 -1: report an infinite number of warnings.
423 Controls whether the panic kmsg data should be reported to Hyper-V.
431 ignore-unaligned-usertrap
445 See also `unaligned-trap`_ and `unaligned-dump-stack`_. On ``ia64``,
483 The correct long-term solution is to do the permission checks at
556 By default they are equal to -1, which means generic allocation logic.
562 2) Toggle with non-default value will be set back to -1 by kernel after
564 fails, it is undefined if the value remains unmodified or is reset to -1.
588 that are programmed to generate Non-Maskable Interrupts (NMIs) periodically
597 Documentation/admin-guide/kernel-parameters.rst).
648 promotion throughput. The per-node max promotion throughput in MB/s
666 1: Will non-maskably interrupt all CPUs and dump their backtraces when
687 The only way to tune these values is to rebuild the kernel :-)
693 if your architecture did not always support 32-bit UIDs (i.e. arm,
694 i386, m68k, sh, and sparc32), a fixed UID and GID will be returned to
695 applications that use the old 16-bit UID/GID system calls, if the
696 actual UID or GID would exceed 65535.
698 These sysctls allow you to change the value of the fixed UID and GID.
727 servers issue this sort of NMI when the dump button is pushed,
739 1 Panic immediately. If the `panic` sysctl is also non-zero then the
840 1-100 Attempt to throttle perf's sample rate to this
863 -1 Allow use of (almost) all events by all users.
884 '``perf record -g``' or '``perf trace --call-graph fp``'.
887 enabled, otherwise writing to this file will return ``-EBUSY``.
895 Control size of per-cpu ring buffer not counted against mlock limit.
905 instance, when using '``perf record -g``' or '``perf trace --call-graph fp``'.
908 enabled, otherwise writing to this file will return ``-EBUSY``.
940 powersave-nap (PPC only)
943 If set, Linux-PPC will use the 'nap' mode of powersaving,
976 Value from 0 - 10000 is allowed.
1012 a one-time setting until next reboot: once set, it cannot be changed by
1064 loaded to random addresses. Also for PIE-linked binaries, the
1075 non-legacy applications that would be broken this way, so for most
1084 real-root-dev
1087 See Documentation/admin-guide/initrd.rst.
1090 reboot-cmd (SPARC only)
1112 Documentation/accounting/delay-accounting.rst. Enabling this feature incurs
1181 See Documentation/userspace-api/seccomp_filter.rst.
1184 sg-big-buff
1254 -1 Legacy per-write sysctl value handling, with no printk warnings.
1335 stop-a (SPARC only)
1338 Controls Stop-A:
1341 0 Stop-A has no effect.
1342 1 Stop-A breaks to the PROM (default).
1345 Stop-A is always enabled on a panic, so that the user can return to
1352 See Documentation/admin-guide/sysrq.rst.
1358 Non-zero if the kernel has been tainted. Numeric values, which can be
1374 4096 `(O)` externally-built ("out-of-tree") module was loaded
1382 See Documentation/admin-guide/tainted-kernels.rst for more information.
1389 See Documentation/admin-guide/kernel-parameters.rst for more details on
1393 threads-max
1403 The minimum value that can be written to ``threads-max`` is 1.
1405 The maximum value that can be written to ``threads-max`` is given by the
1408 If a value outside of this range is written to ``threads-max`` an
1435 See Documentation/admin-guide/kernel-parameters.rst and
1436 Documentation/trace/boottime-trace.rst.
1439 .. _unaligned-dump-stack:
1441 unaligned-dump-stack (ia64)
1452 See also `ignore-unaligned-usertrap`_.
1455 unaligned-trap
1468 See also `ignore-unaligned-usertrap`_.
1475 value is non-zero, unknown NMI is trapped and then panic occurs. At
1487 will return ``-EPERM``. Once set to 1, this can't be cleared from the
1536 to re-enable cores that by default were not running the watchdog,
1543 echo 0,2-4 > /proc/sys/kernel/watchdog_cpumask