{ "content": [ { "type": "text", "text": "# SYSTEMD-SYSTEM.CONF (man)\n\n## NAME\n\nsystemd-system.conf, system.conf.d, systemd-user.conf, user.conf.d - System and session service manager configuration files\n\n## SYNOPSIS\n\n/etc/systemd/system.conf, /etc/systemd/system.conf.d/*.conf,\n/run/systemd/system.conf.d/*.conf, /lib/systemd/system.conf.d/*.conf\n~/.config/systemd/user.conf, /etc/systemd/user.conf, /etc/systemd/user.conf.d/*.conf,\n/run/systemd/user.conf.d/*.conf, /usr/lib/systemd/user.conf.d/*.conf\n\n## DESCRIPTION\n\nWhen run as a system instance, systemd interprets the configuration file system.conf and the\nfiles in system.conf.d directories; when run as a user instance, it interprets the\nconfiguration file user.conf (either in the home directory of the user, or if not found,\nunder /etc/systemd/) and the files in user.conf.d directories. These configuration files\ncontain a few settings controlling basic manager operations.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **CONFIGURATION DIRECTORIES AND PRECEDENCE**\n- **OPTIONS**\n- **SPECIFIERS** (1 subsections)\n- **SEE ALSO**\n- **NOTES**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "SYSTEMD-SYSTEM.CONF", "section": "", "mode": "man", "summary": "systemd-system.conf, system.conf.d, systemd-user.conf, user.conf.d - System and session service manager configuration files", "synopsis": "/etc/systemd/system.conf, /etc/systemd/system.conf.d/*.conf,\n/run/systemd/system.conf.d/*.conf, /lib/systemd/system.conf.d/*.conf\n~/.config/systemd/user.conf, /etc/systemd/user.conf, /etc/systemd/user.conf.d/*.conf,\n/run/systemd/user.conf.d/*.conf, /usr/lib/systemd/user.conf.d/*.conf", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [ { "name": "systemd", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/systemd/1/json" }, { "name": "systemd.directives", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/systemd.directives/7/json" }, { "name": "systemd.exec", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/systemd.exec/5/json" }, { "name": "systemd.service", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/systemd.service/5/json" }, { "name": "environ", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/environ/7/json" }, { "name": "capabilities", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/capabilities/7/json" } ], "section_outline": [ { "name": "NAME", "lines": 3, "subsections": [] }, { "name": "SYNOPSIS", "lines": 6, "subsections": [] }, { "name": "DESCRIPTION", "lines": 8, "subsections": [] }, { "name": "CONFIGURATION DIRECTORIES AND PRECEDENCE", "lines": 27, "subsections": [] }, { "name": "OPTIONS", "lines": 218, "subsections": [] }, { "name": "SPECIFIERS", "lines": 3, "subsections": [ { "name": "Table 1. Specifiers available", "lines": 116 } ] }, { "name": "SEE ALSO", "lines": 3, "subsections": [] }, { "name": "NOTES", "lines": 9, "subsections": [] } ], "sections": { "NAME": { "content": "systemd-system.conf, system.conf.d, systemd-user.conf, user.conf.d - System and session\nservice manager configuration files\n", "subsections": [] }, "SYNOPSIS": { "content": "/etc/systemd/system.conf, /etc/systemd/system.conf.d/*.conf,\n/run/systemd/system.conf.d/*.conf, /lib/systemd/system.conf.d/*.conf\n\n~/.config/systemd/user.conf, /etc/systemd/user.conf, /etc/systemd/user.conf.d/*.conf,\n/run/systemd/user.conf.d/*.conf, /usr/lib/systemd/user.conf.d/*.conf\n", "subsections": [] }, "DESCRIPTION": { "content": "When run as a system instance, systemd interprets the configuration file system.conf and the\nfiles in system.conf.d directories; when run as a user instance, it interprets the\nconfiguration file user.conf (either in the home directory of the user, or if not found,\nunder /etc/systemd/) and the files in user.conf.d directories. These configuration files\ncontain a few settings controlling basic manager operations.\n\nSee systemd.syntax(7) for a general description of the syntax.\n", "subsections": [] }, "CONFIGURATION DIRECTORIES AND PRECEDENCE": { "content": "The default configuration is set during compilation, so configuration is only needed when it\nis necessary to deviate from those defaults. Initially, the main configuration file in\n/etc/systemd/ contains commented out entries showing the defaults as a guide to the\nadministrator. Local overrides can be created by editing this file or by creating drop-ins,\nas described below. Using drop-ins for local configuration is recommended over modifications\nto the main configuration file.\n\nIn addition to the \"main\" configuration file, drop-in configuration snippets are read from\n/usr/lib/systemd/*.conf.d/, /usr/local/lib/systemd/*.conf.d/, and /etc/systemd/*.conf.d/.\nThose drop-ins have higher precedence and override the main configuration file. Files in the\n*.conf.d/ configuration subdirectories are sorted by their filename in lexicographic order,\nregardless of in which of the subdirectories they reside. When multiple files specify the\nsame option, for options which accept just a single value, the entry in the file sorted last\ntakes precedence, and for options which accept a list of values, entries are collected as\nthey occur in the sorted files.\n\nWhen packages need to customize the configuration, they can install drop-ins under /usr/.\nFiles in /etc/ are reserved for the local administrator, who may use this logic to override\nthe configuration files installed by vendor packages. Drop-ins have to be used to override\npackage drop-ins, since the main configuration file has lower precedence. It is recommended\nto prefix all filenames in those subdirectories with a two-digit number and a dash, to\nsimplify the ordering of the files.\n\nTo disable a configuration file supplied by the vendor, the recommended way is to place a\nsymlink to /dev/null in the configuration directory in /etc/, with the same filename as the\nvendor configuration file.\n", "subsections": [] }, "OPTIONS": { "content": "All options are configured in the [Manager] section:\n\nLogColor=, LogLevel=, LogLocation=, LogTarget=, LogTime=, DumpCore=yes, CrashChangeVT=no,\nCrashShell=no, CrashReboot=no, ShowStatus=yes, DefaultStandardOutput=journal,\nDefaultStandardError=inherit\nConfigures various parameters of basic manager operation. These options may be overridden\nby the respective process and kernel command line arguments. See systemd(1) for details.\n\nCtrlAltDelBurstAction=\nDefines what action will be performed if user presses Ctrl-Alt-Delete more than 7 times\nin 2s. Can be set to \"reboot-force\", \"poweroff-force\", \"reboot-immediate\",\n\"poweroff-immediate\" or disabled with \"none\". Defaults to \"reboot-force\".\n\nCPUAffinity=\nConfigures the CPU affinity for the service manager as well as the default CPU affinity\nfor all forked off processes. Takes a list of CPU indices or ranges separated by either\nwhitespace or commas. CPU ranges are specified by the lower and upper CPU indices\nseparated by a dash. This option may be specified more than once, in which case the\nspecified CPU affinity masks are merged. If the empty string is assigned, the mask is\nreset, all assignments prior to this will have no effect. Individual services may\noverride the CPU affinity for their processes with the CPUAffinity= setting in unit\nfiles, see systemd.exec(5).\n\nNUMAPolicy=\nConfigures the NUMA memory policy for the service manager and the default NUMA memory\npolicy for all forked off processes. Individual services may override the default policy\nwith the NUMAPolicy= setting in unit files, see systemd.exec(5).\n\nNUMAMask=\nConfigures the NUMA node mask that will be associated with the selected NUMA policy. Note\nthat default and local NUMA policies don't require explicit NUMA node mask and value of\nthe option can be empty. Similarly to NUMAPolicy=, value can be overridden by individual\nservices in unit files, see systemd.exec(5).\n\nRuntimeWatchdogSec=, RebootWatchdogSec=, KExecWatchdogSec=\nConfigure the hardware watchdog at runtime and at reboot. Takes a timeout value in\nseconds (or in other time units if suffixed with \"ms\", \"min\", \"h\", \"d\", \"w\"). If\nRuntimeWatchdogSec= is set to a non-zero value, the watchdog hardware (/dev/watchdog or\nthe path specified with WatchdogDevice= or the kernel option systemd.watchdog-device=)\nwill be programmed to automatically reboot the system if it is not contacted within the\nspecified timeout interval. The system manager will ensure to contact it at least once in\nhalf the specified timeout interval. This feature requires a hardware watchdog device to\nbe present, as it is commonly the case in embedded and server systems. Not all hardware\nwatchdogs allow configuration of all possible reboot timeout values, in which case the\nclosest available timeout is picked. RebootWatchdogSec= may be used to configure the\nhardware watchdog when the system is asked to reboot. It works as a safety net to ensure\nthat the reboot takes place even if a clean reboot attempt times out. Note that the\nRebootWatchdogSec= timeout applies only to the second phase of the reboot, i.e. after all\nregular services are already terminated, and after the system and service manager process\n(PID 1) got replaced by the systemd-shutdown binary, see system bootup(7) for details.\nDuring the first phase of the shutdown operation the system and service manager remains\nrunning and hence RuntimeWatchdogSec= is still honoured. In order to define a timeout on\nthis first phase of system shutdown, configure JobTimeoutSec= and JobTimeoutAction= in\nthe [Unit] section of the shutdown.target unit. By default RuntimeWatchdogSec= defaults\nto 0 (off), and RebootWatchdogSec= to 10min. KExecWatchdogSec= may be used to\nadditionally enable the watchdog when kexec is being executed rather than when rebooting.\nNote that if the kernel does not reset the watchdog on kexec (depending on the specific\nhardware and/or driver), in this case the watchdog might not get disabled after kexec\nsucceeds and thus the system might get rebooted, unless RuntimeWatchdogSec= is also\nenabled at the same time. For this reason it is recommended to enable KExecWatchdogSec=\nonly if RuntimeWatchdogSec= is also enabled. These settings have no effect if a hardware\nwatchdog is not available.\n\nWatchdogDevice=\nConfigure the hardware watchdog device that the runtime and shutdown watchdog timers will\nopen and use. Defaults to /dev/watchdog. This setting has no effect if a hardware\nwatchdog is not available.\n\nCapabilityBoundingSet=\nControls which capabilities to include in the capability bounding set for PID 1 and its\nchildren. See capabilities(7) for details. Takes a whitespace-separated list of\ncapability names as read by capfromname(3). Capabilities listed will be included in the\nbounding set, all others are removed. If the list of capabilities is prefixed with ~, all\nbut the listed capabilities will be included, the effect of the assignment inverted. Note\nthat this option also affects the respective capabilities in the effective, permitted and\ninheritable capability sets. The capability bounding set may also be individually\nconfigured for units using the CapabilityBoundingSet= directive for units, but note that\ncapabilities dropped for PID 1 cannot be regained in individual units, they are lost for\ngood.\n\nNoNewPrivileges=\nTakes a boolean argument. If true, ensures that PID 1 and all its children can never gain\nnew privileges through execve(2) (e.g. via setuid or setgid bits, or filesystem\ncapabilities). Defaults to false. General purpose distributions commonly rely on\nexecutables with setuid or setgid bits and will thus not function properly with this\noption enabled. Individual units cannot disable this option. Also see No New Privileges\nFlag[1].\n\nSystemCallArchitectures=\nTakes a space-separated list of architecture identifiers. Selects from which\narchitectures system calls may be invoked on this system. This may be used as an\neffective way to disable invocation of non-native binaries system-wide, for example to\nprohibit execution of 32-bit x86 binaries on 64-bit x86-64 systems. This option operates\nsystem-wide, and acts similar to the SystemCallArchitectures= setting of unit files, see\nsystemd.exec(5) for details. This setting defaults to the empty list, in which case no\nfiltering of system calls based on architecture is applied. Known architecture\nidentifiers are \"x86\", \"x86-64\", \"x32\", \"arm\" and the special identifier \"native\". The\nlatter implicitly maps to the native architecture of the system (or more specifically,\nthe architecture the system manager was compiled for). Set this setting to \"native\" to\nprohibit execution of any non-native binaries. When a binary executes a system call of an\narchitecture that is not listed in this setting, it will be immediately terminated with\nthe SIGSYS signal.\n\nTimerSlackNSec=\nSets the timer slack in nanoseconds for PID 1, which is inherited by all executed\nprocesses, unless overridden individually, for example with the TimerSlackNSec= setting\nin service units (for details see systemd.exec(5)). The timer slack controls the accuracy\nof wake-ups triggered by system timers. See prctl(2) for more information. Note that in\ncontrast to most other time span definitions this parameter takes an integer value in\nnano-seconds if no unit is specified. The usual time units are understood too.\n\nStatusUnitFormat=\nTakes name, description or combined as the value. If name, the system manager will use\nunit names in status messages (e.g. \"systemd-journald.service\"), instead of the longer\nand more informative descriptions set with Description= (e.g. \"Journal Logging\nService\"). If combined, the system manager will use both unit names and descriptions in\nstatus messages (e.g. \"systemd-journald.service - Journal Logging Service\").\n\nSee systemd.unit(5) for details about unit names and Description=.\n\nDefaultTimerAccuracySec=\nSets the default accuracy of timer units. This controls the global default for the\nAccuracySec= setting of timer units, see systemd.timer(5) for details. AccuracySec= set\nin individual units override the global default for the specific unit. Defaults to 1min.\nNote that the accuracy of timer units is also affected by the configured timer slack for\nPID 1, see TimerSlackNSec= above.\n\nDefaultTimeoutStartSec=, DefaultTimeoutStopSec=, DefaultTimeoutAbortSec=, DefaultRestartSec=\nConfigures the default timeouts for starting, stopping and aborting of units, as well as\nthe default time to sleep between automatic restarts of units, as configured per-unit in\nTimeoutStartSec=, TimeoutStopSec=, TimeoutAbortSec= and RestartSec= (for services, see\nsystemd.service(5) for details on the per-unit settings). Disabled by default, when\nservice with Type=oneshot is used. For non-service units, DefaultTimeoutStartSec= sets\nthe default TimeoutSec= value. DefaultTimeoutStartSec= and DefaultTimeoutStopSec=\ndefault to 90s. DefaultTimeoutAbortSec= is not set by default so that all units fall\nback to TimeoutStopSec=. DefaultRestartSec= defaults to 100ms.\n\nDefaultStartLimitIntervalSec=, DefaultStartLimitBurst=\nConfigure the default unit start rate limiting, as configured per-service by\nStartLimitIntervalSec= and StartLimitBurst=. See systemd.service(5) for details on the\nper-service settings. DefaultStartLimitIntervalSec= defaults to 10s.\nDefaultStartLimitBurst= defaults to 5.\n\nDefaultEnvironment=\nConfigures environment variables passed to all executed processes. Takes a\nspace-separated list of variable assignments. See environ(7) for details about\nenvironment variables.\n\nSimple \"%\"-specifier expansion is supported, see below for a list of supported\nspecifiers.\n\nExample:\n\nDefaultEnvironment=\"VAR1=word1 word2\" VAR2=word3 \"VAR3=word 5 6\"\n\nSets three variables \"VAR1\", \"VAR2\", \"VAR3\".\n\nManagerEnvironment=\nTakes the same arguments as DefaultEnvironment=, see above. Sets environment variables\njust for the manager process itself. In contrast to user managers, these variables are\nnot inherited by processes spawned by the system manager, use DefaultEnvironment= for\nthat. Note that these variables are merged into the existing environment block. In\nparticular, in case of the system manager, this includes variables set by the kernel\nbased on the kernel command line.\n\nSetting environment variables for the manager process may be useful to modify its\nbehaviour. See ENVIRONMENT[2] for a descriptions of some variables understood by systemd.\n\nSimple \"%\"-specifier expansion is supported, see below for a list of supported\nspecifiers.\n\nDefaultCPUAccounting=, DefaultBlockIOAccounting=, DefaultMemoryAccounting=,\nDefaultTasksAccounting=, DefaultIOAccounting=, DefaultIPAccounting=\nConfigure the default resource accounting settings, as configured per-unit by\nCPUAccounting=, BlockIOAccounting=, MemoryAccounting=, TasksAccounting=, IOAccounting=\nand IPAccounting=. See systemd.resource-control(5) for details on the per-unit settings.\nDefaultTasksAccounting= defaults to yes, DefaultMemoryAccounting= to yes.\nDefaultCPUAccounting= defaults to yes if enabling CPU accounting doesn't require the CPU\ncontroller to be enabled (Linux 4.15+ using the unified hierarchy for resource control),\notherwise it defaults to no. The other three settings default to no.\n\nDefaultTasksMax=\nConfigure the default value for the per-unit TasksMax= setting. See systemd.resource-\ncontrol(5) for details. This setting applies to all unit types that support resource\ncontrol settings, with the exception of slice units. Defaults to 15% of the minimum of\nkernel.pidmax=, kernel.threads-max= and root cgroup pids.max. Kernel has a default value\nfor kernel.pidmax= and an algorithm of counting in case of more than 32 cores. For\nexample with the default kernel.pidmax=, DefaultTasksMax= defaults to 4915, but might be\ngreater in other systems or smaller in OS containers.\n\nDefaultLimitCPU=, DefaultLimitFSIZE=, DefaultLimitDATA=, DefaultLimitSTACK=,\nDefaultLimitCORE=, DefaultLimitRSS=, DefaultLimitNOFILE=, DefaultLimitAS=,\nDefaultLimitNPROC=, DefaultLimitMEMLOCK=, DefaultLimitLOCKS=, DefaultLimitSIGPENDING=,\nDefaultLimitMSGQUEUE=, DefaultLimitNICE=, DefaultLimitRTPRIO=, DefaultLimitRTTIME=\nThese settings control various default resource limits for processes executed by units.\nSee setrlimit(2) for details. These settings may be overridden in individual units using\nthe corresponding LimitXXX= directives and they accept the same parameter syntax, see\nsystemd.exec(5) for details. Note that these resource limits are only defaults for units,\nthey are not applied to the service manager process (i.e. PID 1) itself.\n\nMost of these settings are unset, which means the resource limits are inherited from the\nkernel or, if invoked in a container, from the container manager. However, the following\nhave defaults:\n\n• DefaultLimitNOFILE= defaults to \"1024:524288\".\n\n• DefaultLimitCORE= does not have a default but it is worth mentioning that RLIMITCORE\nis set to \"infinity\" by PID 1 which is inherited by its children.\n\n• Note that the service manager internally increases RLIMITMEMLOCK for itself, however\nthe limit is reverted to the original value for child processes forked off.\n\nDefaultOOMPolicy=\nConfigure the default policy for reacting to processes being killed by the Linux\nOut-Of-Memory (OOM) killer. This may be used to pick a global default for the per-unit\nOOMPolicy= setting. See systemd.service(5) for details. Note that this default is not\nused for services that have Delegate= turned on.\n", "subsections": [] }, "SPECIFIERS": { "content": "Specifiers may be used in the DefaultEnvironment= and ManagerEnvironment= settings. The\nfollowing expansions are understood:\n", "subsections": [ { "name": "Table 1. Specifiers available", "content": "┌──────────┬───────────────────────────┬───────────────────────────┐\n│Specifier │ Meaning │ Details │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%a\" │ Architecture │ A short string │\n│ │ │ identifying the │\n│ │ │ architecture of the local │\n│ │ │ system. A string such as │\n│ │ │ x86, x86-64 or arm64. See │\n│ │ │ the architectures defined │\n│ │ │ for │\n│ │ │ ConditionArchitecture= in │\n│ │ │ systemd.unit(5) for a │\n│ │ │ full list. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%A\" │ Operating system image │ The operating system │\n│ │ version │ image version identifier │\n│ │ │ of the running system, as │\n│ │ │ read from the │\n│ │ │ IMAGEVERSION= field of │\n│ │ │ /etc/os-release. If not │\n│ │ │ set, resolves to an empty │\n│ │ │ string. See os-release(5) │\n│ │ │ for more information. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%b\" │ Boot ID │ The boot ID of the │\n│ │ │ running system, formatted │\n│ │ │ as string. See random(4) │\n│ │ │ for more information. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%B\" │ Operating system build ID │ The operating system │\n│ │ │ build identifier of the │\n│ │ │ running system, as read │\n│ │ │ from the BUILDID= field │\n│ │ │ of /etc/os-release. If │\n│ │ │ not set, resolves to an │\n│ │ │ empty string. See os- │\n│ │ │ release(5) for more │\n│ │ │ information. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%H\" │ Host name │ The hostname of the │\n│ │ │ running system. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%l\" │ Short host name │ The hostname of the │\n│ │ │ running system, truncated │\n│ │ │ at the first dot to │\n│ │ │ remove any domain │\n│ │ │ component. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%m\" │ Machine ID │ The machine ID of the │\n│ │ │ running system, formatted │\n│ │ │ as string. See machine- │\n│ │ │ id(5) for more │\n│ │ │ information. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%M\" │ Operating system image │ The operating system │\n│ │ identifier │ image identifier of the │\n│ │ │ running system, as read │\n│ │ │ from the IMAGEID= field │\n│ │ │ of /etc/os-release. If │\n│ │ │ not set, resolves to an │\n│ │ │ empty string. See os- │\n│ │ │ release(5) for more │\n│ │ │ information. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%o\" │ Operating system ID │ The operating system │\n│ │ │ identifier of the running │\n│ │ │ system, as read from the │\n│ │ │ ID= field of │\n│ │ │ /etc/os-release. See os- │\n│ │ │ release(5) for more │\n│ │ │ information. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%v\" │ Kernel release │ Identical to uname -r │\n│ │ │ output. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%w\" │ Operating system version │ The operating system │\n│ │ ID │ version identifier of the │\n│ │ │ running system, as read │\n│ │ │ from the VERSIONID= │\n│ │ │ field of /etc/os-release. │\n│ │ │ If not set, resolves to │\n│ │ │ an empty string. See os- │\n│ │ │ release(5) for more │\n│ │ │ information. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%W\" │ Operating system variant │ The operating system │\n│ │ ID │ variant identifier of the │\n│ │ │ running system, as read │\n│ │ │ from the VARIANTID= │\n│ │ │ field of /etc/os-release. │\n│ │ │ If not set, resolves to │\n│ │ │ an empty string. See os- │\n│ │ │ release(5) for more │\n│ │ │ information. │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%T\" │ Directory for temporary │ This is either /tmp or │\n│ │ files │ the path \"$TMPDIR\", │\n│ │ │ \"$TEMP\" or \"$TMP\" are set │\n│ │ │ to. (Note that the │\n│ │ │ directory may be │\n│ │ │ specified without a │\n│ │ │ trailing slash.) │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%V\" │ Directory for larger and │ This is either /var/tmp │\n│ │ persistent temporary │ or the path \"$TMPDIR\", │\n│ │ files │ \"$TEMP\" or \"$TMP\" are set │\n│ │ │ to. (Note that the │\n│ │ │ directory may be │\n│ │ │ specified without a │\n│ │ │ trailing slash.) │\n├──────────┼───────────────────────────┼───────────────────────────┤\n│\"%%\" │ Single percent sign │ Use \"%%\" in place of \"%\" │\n│ │ │ to specify a single │\n│ │ │ percent sign. │\n└──────────┴───────────────────────────┴───────────────────────────┘\n" } ] }, "SEE ALSO": { "content": "systemd(1), systemd.directives(7), systemd.exec(5), systemd.service(5), environ(7),\ncapabilities(7)\n", "subsections": [] }, "NOTES": { "content": "1. No New Privileges Flag\nhttps://www.kernel.org/doc/html/latest/userspace-api/nonewprivs.html\n\n2. ENVIRONMENT\nhttps://systemd.io/ENVIRONMENT\n\n\n\nsystemd 249 SYSTEMD-SYSTEM.CONF(5)", "subsections": [] } } } }