summaryrefslogtreecommitdiffstats
path: root/man/systemd-system.conf.xml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* license: LGPL-2.1+ -> LGPL-2.1-or-laterYu Watanabe2020-11-091-1/+1
|
* man: fix some manvolnumAnita Zhang2020-07-111-1/+1
|
* tree-wide: drop quotes from around [section]Zbigniew Jędrzejewski-Szmek2020-07-061-2/+2
| | | | | | | For users, the square brackets already serve as markup and clearly delineate the section name from surrounding text. Putting additional markup around that only adds clutter. Also, we were very inconsistent in using the quotes. Let's just drop them altogether.
* tree-wide: fixes for assorted grammar and spelling issuesZbigniew Jędrzejewski-Szmek2020-07-061-3/+3
| | | | Fixes #16363. Also includes some changes where I generalized the pattern.
* log: add support for prefixing console log messages with current timestampDan Streetman2020-02-101-0/+1
|
* man: sort log parameters in alphabetical orderDan Streetman2020-02-101-2/+2
| | | | | This only sorts the --log-* params in order in the man page docs; no text is added or removed or modified.
* man: clarify that user rlimits cannot go beyond limits set for service mgrLennart Poettering2020-01-171-24/+8
| | | | Fixes: #10758
* core: rename ShutdownWatchdogSec to RebootWatchdogSecLuca Boccassi2019-07-231-4/+4
| | | | | | | This option is only used on reboot, not on other types of shutdown modes, so it is misleading. Keep the old name working for backward compatibility, but remove it from the documentation.
* core: add KExecWatchdogSec optionLuca Boccassi2019-07-231-1/+8
| | | | | | | | | | | Rather than always enabling the shutdown WD on kexec, which might be dangerous in case the kernel driver and/or the hardware implementation does not reset the wd on kexec, add a new timer, disabled by default, to let users optionally enable the shutdown WD on kexec separately from the runtime and reboot ones. Advise in the documentation to also use the runtime WD in conjunction with it. Fixes: a637d0f9ecbe ("core: set shutdown watchdog on kexec too")
* Add config and kernel commandline option to use short identifiersZbigniew Jędrzejewski-Szmek2019-07-101-0/+10
| | | | | | | No functional change, just docs and configuration and parsing. v2: - change ShortIdentifiers=yes|no to StatusUnitFormat=name|description.
* docs: fix typos and duplicate wordsMichael Prokop2019-06-271-1/+1
| | | | | | | | | s/and and/and/ s/explicity/explicitly/ s/that that/that/ s/the the/the/ s/is is/it is/ s/overriden/overridden/
* core: introduce NUMAPolicy and NUMAMask optionsMichal Sekletar2019-06-241-0/+19
| | | | | | | | | | | | | Make possible to set NUMA allocation policy for manager. Manager's policy is by default inherited to all forked off processes. However, it is possible to override the policy on per-service basis. Currently we support, these policies: default, prefer, bind, interleave, local. See man 2 set_mempolicy for details on each policy. Overall NUMA policy actually consists of two parts. Policy itself and bitmask representing NUMA nodes where is policy effective. Node mask can be specified using related option, NUMAMask. Default mask can be overwritten on per-service level.
* pid1: parse CPUAffinity= in incremental fashionZbigniew Jędrzejewski-Szmek2019-05-291-4/+7
| | | | | | | | This makes the handling of this option match what we do in unit files. I think consistency is important here. (As it happens, it is the only option in system.conf that is "non-atomic", i.e. where there's a list of things which can be split over multiple assignments. All other options are single-valued, so there's no issue of how to handle multiple assignments.)
* service: handle abort stops with dedicated timeoutJan Klötzke2019-04-121-4/+8
| | | | | | | | | | | | | | | | | When shooting down a service with SIGABRT the user might want to have a much longer stop timeout than on regular stops/shutdowns. Especially in the face of short stop timeouts the time might not be sufficient to write huge core dumps before the service is killed. This commit adds a dedicated (Default)TimeoutAbortSec= timer that is used when stopping a service via SIGABRT. In all other cases the existing TimeoutStopSec= is used. The timer value is unset by default to skip the special handling and use TimeoutStopSec= for state 'stop-watchdog' to keep the old behaviour. If the service is in state 'stop-watchdog' and the service should be stopped explicitly we still go to 'stop-sigterm' and re-apply the usual TimeoutStopSec= timeout.
* man: document new OOMPolicy= settingLennart Poettering2019-04-091-0/+11
|
* man: use same header for all filesZbigniew Jędrzejewski-Szmek2019-03-141-1/+1
| | | | | | | The "include" files had type "book" for some raeason. I don't think this is meaningful. Let's just use the same everywhere. $ perl -i -0pe 's^..DOCTYPE (book|refentry) PUBLIC "-//OASIS//DTD DocBook XML V4.[25]//EN"\s+"http^<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"\n "http^gms' man/*.xml
* man: standarize on one-line license headerZbigniew Jędrzejewski-Szmek2019-03-141-4/+1
| | | | | | No need to waste space, and uniformity is good. $ perl -i -0pe 's|\n+<!--\s*SPDX-License-Identifier: LGPL-2.1..\s*-->|\n<!-- SPDX-License-Identifier: LGPL-2.1+ -->|gms' man/*.xml
* man: move all config file options to one sectionZbigniew Jędrzejewski-Szmek2019-02-131-1/+1
| | | | | | We had "SYSTEM MANAGER DIRECTIVES" which was a misnomer already, because it also listed user manager stuff. Let's make this a more general section and move the items for other services there too (from "MISCELANENOUS").
* Update systemd-system.conf.xmlMikhail Kasimov2019-01-151-1/+3
| | | Updating due to phrase "Defaults to DefaultTimeoutStartSec= from the manager configuration file, except when Type=oneshot is used, in which case the timeout is disabled by default (see systemd-system.conf)" from [0] https://github.com/systemd/systemd/blob/master/man/systemd.service.xml
* cgroup v2: DefaultCPUAccounting=yes if CPU controller isn't requiredChris Down2018-11-181-2/+3
| | | | | | | | We now don't enable the CPU controller just for CPU accounting if we are on 4.15+ and using pure unified hierarchy, as this is provided externally to the CPU controller. This makes CPUAccounting=yes essentially free, so enabling it by default when it's cheap seems like a good idea.
* core: remove JoinControllers= configuration settingLennart Poettering2018-11-161-23/+0
| | | | | | | | | | | | | | | | This removes the ability to configure which cgroup controllers to mount together. Instead, we'll now hardcode that "cpu" and "cpuacct" are mounted together as well as "net_cls" and "net_prio". The concept of mounting controllers together has no future as it does not exist to cgroupsv2. Moreover, the current logic is systematically broken, as revealed by the discussions in #10507. Also, we surveyed Red Hat customers and couldn't find a single user of the concept (which isn't particularly surprising, as it is broken...) This reduced the (already way too complex) cgroup handling for us, since we now know whenever we make a change to a cgroup for one controller to which other controllers it applies.
* man: fix wording a bit on the cgroup accountings options (#10509)Lennart Poettering2018-10-241-3/+3
| | | | | | | | | The &MEMORY_ACCOUNTING_DEFAULT; resolves to "yes" or "no" while the rest of the paragraph talked about "on" and "off". Let's adjust this and stick to "yes" and "no"... Quite frankly I think it's not a particularly good idea to change the docs based configuration changes... THis can only be incomplete, and the wording is still very awkward since we repeat the same sentence twice.
* man: document CPUAffinity= in system.conf in more detailLennart Poettering2018-07-251-5/+5
| | | | Fixes: #9692
* man: drop mode line in file headersZbigniew Jędrzejewski-Szmek2018-07-031-1/+1
| | | | | This is already included in .dir-locals, so we don't need it in the files themselves.
* man: add missing option for system.confYu Watanabe2018-06-251-2/+3
|
* man: drop unused <authorgroup> tags from man sourcesZbigniew Jędrzejewski-Szmek2018-06-141-9/+0
| | | | | | | | | | | | Docbook styles required those to be present, even though the templates that we use did not show those names anywhere. But something changed semi-recently (I would suspect docbook templates, but there was only a minor version bump in recent years, and the changelog does not suggest anything related), and builds now work without those entries. Let's drop this dead weight. Tested with F26-F29, debian unstable. $ perl -i -0pe 's/\s*<authorgroup>.*<.authorgroup>//gms' man/*xml
* tree-wide: remove Lennart's copyright linesLennart Poettering2018-06-141-2/+0
| | | | | | | | | | | These lines are generally out-of-date, incomplete and unnecessary. With SPDX and git repository much more accurate and fine grained information about licensing and authorship is available, hence let's drop the per-file copyright notice. Of course, removing copyright lines of others is problematic, hence this commit only removes my own lines and leaves all others untouched. It might be nicer if sooner or later those could go away too, making git the only and accurate source of authorship information.
* tree-wide: drop 'This file is part of systemd' blurbLennart Poettering2018-06-141-2/+0
| | | | | | | | | | | | | | | | This part of the copyright blurb stems from the GPL use recommendations: https://www.gnu.org/licenses/gpl-howto.en.html The concept appears to originate in times where version control was per file, instead of per tree, and was a way to glue the files together. Ultimately, we nowadays don't live in that world anymore, and this information is entirely useless anyway, as people are very welcome to copy these files into any projects they like, and they shouldn't have to change bits that are part of our copyright header for that. hence, let's just get rid of this old cruft, and shorten our codebase a bit.
* man: add a new page with a general description of common syntaxZbigniew Jędrzejewski-Szmek2018-04-181-1/+3
| | | | | | | | We have a common parser, but for the user it might be completely unobvious that the same general rules apply to all those files. Let's add a page about the basic syntax so that the more specific pages don't have to repeat those details.
* tree-wide: drop license boilerplateZbigniew Jędrzejewski-Szmek2018-04-061-13/+0
| | | | | | | | | | Files which are installed as-is (any .service and other unit files, .conf files, .policy files, etc), are left as is. My assumption is that SPDX identifiers are not yet that well known, so it's better to retain the extended header to avoid any doubt. I also kept any copyright lines. We can probably remove them, but it'd nice to obtain explicit acks from all involved authors before doing that.
* Merge pull request #8533 from poettering/bootup-shutdown-phase2Zbigniew Jędrzejewski-Szmek2018-03-231-25/+21
|\ | | | | extend docs on second phase of shutdown and watchdog handling
| * man: watchdog documentation improvementsLennart Poettering2018-03-211-25/+21
| |
* | main: add NoNewPrivileges config option (#8475)juergbi2018-03-211-0/+15
|/ | | This makes it possible to disable new privileges for the whole system.
* meson: add -Dmemory-accounting-default=true|falseZbigniew Jędrzejewski-Szmek2018-02-151-3/+7
| | | | | This makes it easy to set the default for distributions and users which want to default to off because they primarily use older kernels.
* pid1: turn memory accounting on by default nowLennart Poettering2018-02-091-2/+2
| | | | | | | | | | | After discussions with @htejun it appears it's OK now to enable memory accounting by default for all units without affecting system performance too badly. facebook has made good experiences with deploying memory accounting across their infrastructure. This hence turns MemoryAccounting= from opt-in to opt-out, similar to how TasksAccounting= is already handled. The other accounting options remain off, their performance impact is too big still.
* documentation: add description for watchdog device pathEdward A. James2017-12-081-2/+13
| | | | | Document the command line parameter and the system configuration file setting.
* Add SPDX license identifiers to man pagesZbigniew Jędrzejewski-Szmek2017-11-191-0/+2
|
* man: document the new ip accounting and filting directivesDaniel Mack2017-09-221-9/+6
|
* man: improve ShowStatus=/systemd.show_status=/--show-status= documentationLennart Poettering2016-12-211-6/+4
| | | | Fixes: #4928
* man: fix typos (#4527)Jakub Wilk2016-10-311-1/+1
|
* core: use emergency_action for ctr+alt+del burstLukas Nykryn2016-10-211-2/+3
| | | | Fixes #4306
* man: typo fixesThomas Hindoe Paaboel Andersen2016-10-121-1/+1
| | | | A mix of fixes for typos and UK english
* core: add possibility to set action for ctrl-alt-del burst (#4105)Lukáš Nykrýn2016-10-071-0/+11
| | | | | | For some certification, it should not be possible to reboot the machine through ctrl-alt-delete. Currently we suggest our customers to mask the ctrl-alt-delete target, but that is obviously not enough. Patching the keymaps to disable that is really not a way to go for them, because the settings need to be easily checked by some SCAP tools.
* core: change TasksMax= default for system services to 15%Lennart Poettering2016-07-221-5/+4
| | | | | | | | | | | | | | | | | As it turns out 512 is max number of tasks per service is hit by too many applications, hence let's bump it a bit, and make it relative to the system's maximum number of PIDs. With this change the new default is 15%. At the kernel's default pids_max value of 32768 this translates to 4915. At machined's default TasksMax= setting of 16384 this translates to 2457. Why 15%? Because it sounds like a round number and is close enough to 4096 which I was going for, i.e. an eight-fold increase over the old 512 Summary: | on the host | in a container old default | 512 | 512 new default | 4915 | 2457
* core: rename StartLimitInterval= to StartLimitIntervalSec=Lennart Poettering2016-04-291-3/+3
| | | | | | | | | We generally follow the rule that for time settings we suffix the setting name with "Sec" to indicate the default unit if none is specified. The only exception was the rate limiting interval settings. Fix this, and keep the old names for compatibility. Do the same for journald's RateLimitInterval= setting
* core: support <soft:hard> ranges for RLIMIT optionsKarel Zak2015-11-251-7/+20
| | | | | | | | | | | | | | | | | | | The new parser supports: <value> - specify both limits to the same value <soft:hard> - specify both limits the size or time specific suffixes are supported, for example LimitRTTIME=1sec LimitAS=4G:16G The patch introduces parse_rlimit_range() and rlim type (size, sec, usec, etc.) specific parsers. No code is duplicated now. The patch also sync docs for DefaultLimitXXX= and LimitXXX=. References: https://github.com/systemd/systemd/issues/1769
* core: enable TasksMax= for all services by default, and set it to 512Lennart Poettering2015-11-161-2/+4
| | | | | | | | Also, enable TasksAccounting= for all services by default, too. See: http://lists.freedesktop.org/archives/systemd-devel/2015-November/035006.html
* core: add new DefaultTasksMax= setting for system.confLennart Poettering2015-11-131-1/+12
| | | | | This allows initializing the TasksMax= setting of all units by default to some fixed value, instead of leaving it at infinity as before.
* core: support IEC suffixes for RLIMIT stuffKarel Zak2015-11-061-2/+4
| | | | | | | | | | | | | | | | | Let's make things more user-friendly and support for example LimitAS=16G rather than force users to always use LimitAS=16106127360. The change is relevant for options: [Default]Limit{FSIZE,DATA,STACK,CORE,RSS,AS,MEMLOCK,MSGQUEUE} The patch introduces config_parse_bytes_limit(), it's the same as config_parse_limit() but uses parse_size() tu support the suffixes. Addresses: https://github.com/systemd/systemd/issues/1772
* man: Update man page documentation for CPUAffinityFilipe Brandenburger2015-10-281-2/+4
| | | | | | | Document support for commas as a separator and possibility of specifying ranges of CPU indices. Tested by regenerating the manpages locally and reading them on man.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 05:25:57 +0100