summaryrefslogtreecommitdiffstats
path: root/man (follow)
Commit message (Collapse)AuthorAgeFilesLines
* man: document that nspawn's host0 and ve-* interfaces have default config in ↵Lennart Poettering2016-05-091-15/+21
| | | | networkd
* man: link the part about [DHCP] to the DHCP= explanationLennart Poettering2016-05-061-0/+3
|
* man: move IPv6 note to the right sectionLennart Poettering2016-05-061-9/+5
| | | | Make the XML validate again.
* networkd: move the IAID configuration option into the [DHCP] sectionLennart Poettering2016-05-061-6/+7
| | | | It's only relevant to DHCP, and it should be where the DUID is configured too.
* Merge pull request #3190 from poettering/logind-fixesZbigniew Jędrzejewski-Szmek2016-05-061-0/+16
|\
| * logind: enforce a limit on inhibitors we hand outLennart Poettering2016-05-051-0/+7
| | | | | | | | | | | | | | | | For similar reasons as the recent addition of a limit on sessions. Note that we don't enforce a limit on inhibitors per-user currently, but there's an implicit one, since each inhibitor takes up one fd, and fds are limited via RLIMIT_NOFILE, and the limit on the number of processes per user.
| * logind: enforce a limit on current user sessionsLennart Poettering2016-05-051-0/+9
| | | | | | | | | | | | | | | | | | | | | | We really should put limits on all resources we manage, hence add one to the number of concurrent sessions, too. This was previously unbounded, hence set a relatively high limit of 8K by default. Note that most PAM setups will actually invoke pam_systemd prefixed with "-", so that the return code of pam_systemd is ignored, and the login attempt succeeds anyway. On systems like this the session will be created but is not tracked by systemd.
* | core: change default trigger limits for socket unitsLennart Poettering2016-05-051-6/+7
|/ | | | | | | Let's lower the default values a bit, and pick different defaults for Accept=yes and Accept=no sockets. Fixes: #3167
* Merge pull request #3156 from keszybz/duid-settingsLennart Poettering2016-05-042-34/+80
|\ | | | | Rework DUID setting
| * man: add a description of DUIDType and DUIDRawDataZbigniew Jędrzejewski-Szmek2016-05-032-34/+80
| | | | | | | | | | | | | | | | This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
| * man: s/similar/similarly/Zbigniew Jędrzejewski-Szmek2016-05-031-5/+5
| |
* | Merge pull request #3170 from poettering/v230-preparation-fixesLennart Poettering2016-05-041-1/+3
|\ \ | | | | | | make virtualization detection quieter, rework unit start limit logic, detect unit file drop-in changes correctly, fix autofs state propagation
| * | core: move enforcement of the start limit into per-unit-type code againLennart Poettering2016-05-021-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let's move the enforcement of the per-unit start limit from unit.c into the type-specific files again. For unit types that know a concept of "result" codes this allows us to hook up the start limit condition to it with an explicit result code. Also, this makes sure that the state checks in clal like service_start() may be done before the start limit is checked, as the start limit really should be checked last, right before everything has been verified to be in order. The generic start limit logic is left in unit.c, but the invocation of it is moved into the per-type files, in the various xyz_start() functions, so that they may place the check at the right location. Note that this change drops the enforcement entirely from device, slice, target and scope units, since these unit types generally may not fail activation, or may only be activated a single time. This is also documented now. Note that restores the "start-limit-hit" result code that existed before 6bf0f408e4833152197fb38fb10a9989c89f3a59 already in the service code. However, it's not introduced for all units that have a result code concept. Fixes #3166.
* | | networkd: Add support to configure IPv6 preferred lifetime (#3102)Susant Sahani2016-05-031-0/+12
| | | | | | | | | | | | | | | | | | Closes #2166. We only allow 0, infinity and forever. infinity and forever is same.
* | | Merge pull request #3132 from ssahani/route-tableZbigniew Jędrzejewski-Szmek2016-05-031-0/+8
|\ \ \ | | | | | | | | networkd: add support to set route table
| * | | networkd: add support to set route tableSusant Sahani2016-05-031-0/+8
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | networkd: add support to set route table 1. add support to configure the table id. if id is less than 256 we can fit this in the header of route as netlink property is a char. But in kernel this proepty is a unsigned 32. Hence if greater that 256 add this as RTA_TABLE attribute. 2. we are not setting the address family now. Now set this property.
* | | man: rename TriggerLimitIntervalBurst to TriggerLimitBurst (#3181)Evgeny Vereshchagin2016-05-031-1/+1
| | | | | | | | | | | | | | | [/etc/systemd/system/test.socket:2] Unknown lvalue 'TriggerLimitIntervalBurst' in section 'Socket' Follow-up for 8b26cdbd2a94
* | | Merge pull request #3153 from poettering/async-cloneZbigniew Jędrzejewski-Szmek2016-05-021-7/+5
|\ \ \ | |/ / |/| | machined: make "clone" asynchronous, and support copy-based fall-back
| * | man: slightly extend the machinectl clone documentationLennart Poettering2016-05-021-7/+5
| |/
* | Merge pull request #3152 from poettering/aliasfixZbigniew Jędrzejewski-Szmek2016-05-015-30/+28
|\ \ | |/ |/| | | | | Refuse aliases to non-aliasable units in more places Fixes #2730.
| * man: document that some unit types do not support unit aliases via symlinksLennart Poettering2016-04-295-30/+28
| |
* | Merge pull request #3151 from keszybz/pr3149-2Zbigniew Jędrzejewski-Szmek2016-04-291-0/+6
|\ \ | | | | | | Assorted fixes #3149 + one commit tacked on top
| * | man: document that RemainAfterExit= doesn't make much sense for repetitive ↵Lennart Poettering2016-04-291-0/+6
| | | | | | | | | | | | | | | | | | timers Fixes #3122
* | | core: make parsing of RLIMIT_NICE aware of actual nice levelsLennart Poettering2016-04-291-21/+17
| | |
* | | core: rename StartLimitInterval= to StartLimitIntervalSec=Lennart Poettering2016-04-293-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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: move start ratelimiting check after condition checksLennart Poettering2016-04-291-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With #2564 unit start rate limiting was moved from after the condition checks are to before they are made, in an attempt to fix #2467. This however resulted in #2684. However, with a previous commit a concept of per socket unit trigger rate limiting has been added, to fix #2467 more comprehensively, hence the start limit can be moved after the condition checks again, thus fixing #2684. Fixes: #2684
* | | core: introduce activation rate limiting for socket unitsLennart Poettering2016-04-291-0/+16
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | This adds two new settings TriggerLimitIntervalSec= and TriggerLimitBurst= that define a rate limit for activation of socket units. When the limit is hit, the socket is is put into a failure mode. This is an alternative fix for #2467, since the original fix resulted in issue #2684. In a later commit the StartLimitInterval=/StartLimitBurst= rate limiter will be changed to be applied after any start conditions checks are made. This way, there are two separate rate limiters enforced: one at triggering time, before any jobs are queued with this patch, as well as the start limit that is moved again to be run immediately before the unit is activated. Condition checks are done in between the two, and thus no longer affect the start limit.
* | networkd: clean up DUID code a bitLennart Poettering2016-04-291-37/+22
| | | | | | | | | | | | | | | | | | | | | | Let's move DUID configuration into the [DHCP] section, since it only makes sense in a DHCP context, and should be close to the configuration of ClientIdentifier= and suchlike. This really shouldn't be a section of its own, we don't have any for any of our other per-protocol specific identifiers... Follow-up for #2890 #2943
* | man: minor wording fixesLennart Poettering2016-04-291-6/+5
|/ | | | | | As suggested in: https://github.com/systemd/systemd/pull/3124#discussion_r61068789
* core: set start job timeout from the kernel commandline (#3112)tblume2016-04-261-0/+9
| | | | Add the boot parameter: systemd.default_timeout_start_sec to allow modification of the default start job timeout at boot time.
* Merge pull request #3124 from poettering/small-journal-fixesZbigniew Jędrzejewski-Szmek2016-04-261-5/+8
|\
| * man: elaborate on the automatic systemd-journald.socket service dependenciesLennart Poettering2016-04-261-5/+8
| | | | | | | | Fixes: #1603
* | Revert "smaller journal fixes (#3124)"Zbigniew Jędrzejewski-Szmek2016-04-261-8/+5
| | | | | | | | | | | | This reverts commit 6e3930c40f3379b7123e505a71ba4cd6db6c372f. Merge got squashed by mistake.
* | Merge pull request #3093 from poettering/nspawn-userns-magicLennart Poettering2016-04-262-30/+89
|\ \ | | | | | | nspawn automatic user namespaces
| * | nspawn: make -U a tiny bit smarterLennart Poettering2016-04-251-1/+3
| | | | | | | | | | | | | | | With this change -U will turn on user namespacing only if the kernel actually supports it and otherwise gracefully degrade to non-userns mode.
| * | man: document the new user namespacing optionsLennart Poettering2016-04-252-30/+87
| | |
* | | smaller journal fixes (#3124)Lennart Poettering2016-04-261-5/+8
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * sd-journal: detect earlier if we try to read an object from an invalid offset Specifically, detect early if we try to read from offset 0, i.e. are using uninitialized offset data. * journal: when dumping journal contents, react nicer to lines we can't read If journal files are not cleanly closed it might happen that intermediaery journal entries cannot be read. Handle this nicely, skip over the unreadable entries, and log a debug message about it; after all we generally follow the logic that we try to make the best of corrupted files. * journal-file: always generate the same error when encountering corrupted files Let's make sure EBADMSG is the one error we throw when we encounter corrupted data, so that we can neatly test for it. * journal-file: when iterating through a partly corruped journal file, treat error like EOF When we linearly iterate through a corrupted journal file, and we encounter a read error, don't consider this fatal, but merely as EOF condition (and log about it). * journal-file: make seeking in corrupted files work Previously, when we used a bisection table for seeking through a corrupted file, and the end of the bisection table was corrupted we'd most likely fail the entire seek operation. Improve the situation: if we encounter invalid entries in a bisection table, linearly go backwards until we find a working entry again. * man: elaborate on the automatic systemd-journald.socket service dependencies Fixes: #1603
* | man: document the new by-fd journal callsLennart Poettering2016-04-251-26/+35
| | | | | | | | | | Also, remove documentation for sd_journal_open_container() as we consider it deprecated now.
* | man: don't include history sections in man pagesLennart Poettering2016-04-253-45/+0
|/ | | | | | I am pretty sure we shouldn't carry history sections in man pages, since it's very hard to keep them correctly updated, the current ones are very out-of-date, and they tend to make APIs appear unnecessarily complex.
* man: document the default for systemd.timer's Persistent flag (#3099)Evgeny Vereshchagin2016-04-231-1/+2
| | | Closes #3096
* man: don't claim systemd would connect stdout/stderr of daemons with /dev/nullLennart Poettering2016-04-221-8/+6
|
* journalctl: add --no-hostname switchLennart Poettering2016-04-221-0/+7
| | | | | | This suppresses output of the hostname for messages from the local system. Fixes: #2342
* journalctl: add output mode where time is shown in seconds since 1st Jan ↵Lennart Poettering2016-04-221-0/+10
| | | | | | | | 1970 UTC aka "UNIX time". Fixes: #2120
* treewide: fix typos (#3092)Torstein Husebø2016-04-222-2/+2
|
* Merge pull request #3084 from keszybz/preset-fixesLennart Poettering2016-04-221-13/+13
|\ | | | | Nicer error message is symlinking chokes on an existing file
| * systemctl,pid1: do not warn about missing install info with "preset"Zbigniew Jędrzejewski-Szmek2016-04-221-13/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When "preset" was executed for a unit without install info, we'd warn similarly as for "enable" and "disable". But "preset" is usually called for all units, because the preset files are provided by the distribution, and the units are under control of individual programs, and it's reasonable to call "preset" for all units rather then try to do it only for the ones that can be installed. We also don't warn about missing info for "preset-all". Thus it seems reasonable to silently ignore units w/o install info when presetting. (In addition, when more than one unit was specified, we'd issue the warning only if none of them had install info. But this is probably something to fix for enable/disable too.)
* | tree-wide: use mdash instead of a two minusesZbigniew Jędrzejewski-Szmek2016-04-227-7/+7
| |
* | man: document size param of sd_journal_add_matchZbigniew Jędrzejewski-Szmek2016-04-221-5/+13
| | | | | | | | Fixes #1724.
* | Merge pull request #3005 from keszybz/kill-user-procesesLennart Poettering2016-04-213-37/+142
|\ \ | |/ |/| Kill user session scope by default
| * logind: make KillOnlyUsers override KillUserProcessesZbigniew Jędrzejewski-Szmek2016-04-211-12/+13
| | | | | | | | | | | | | | Instead of KillOnlyUsers being a filter for KillUserProcesses, it can now be used to specify users to kill, independently of the KillUserProcesses setting. Having the settings orthogonal seems to make more sense. It also makes KillOnlyUsers symmetrical to KillExcludeUsers.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 04:05:11 +0100