summaryrefslogtreecommitdiffstats
path: root/src (follow)
Commit message (Collapse)AuthorAgeFilesLines
* dissect: show intended architecture of a disk imageLennart Poettering2023-03-013-0/+19
| | | | | We already determine the architecture of disk images and make a choice, and store it per partition. Let's make this accessible globally.
* pid1: add unit file settings to control memory pressure logicLennart Poettering2023-03-0118-16/+209
|
* pid1: also process memory pressure events (and SIGRTMIN+18)Lennart Poettering2023-03-013-1/+78
|
* userdbd: hook up memory pressure and sigrtmin18Lennart Poettering2023-03-012-1/+10
|
* nspawn: hook up memory pressure + sigrtmin+18Lennart Poettering2023-03-011-1/+8
|
* portabled: hook up SIGRTMIN+18 and memory pressureLennart Poettering2023-03-011-1/+10
|
* networkd: hook up SIGRTMIN+18 and memory pressureLennart Poettering2023-03-011-0/+6
|
* importd: hook up memory pressure, SIGRTMIN-18 (and in fact SIGINT + SIGTERM)Lennart Poettering2023-03-011-2/+19
|
* timesyncd: hook up memory pressure + sigrtmin18Lennart Poettering2023-03-012-1/+7
|
* logind: hook up memory pressure + SIGRTMIN+18Lennart Poettering2023-03-011-1/+10
|
* homed: hook up memory pressure/SIGRTMIN+18 handlingLennart Poettering2023-03-012-1/+11
|
* udevd: enable memory pressure/SIGRTMIN+18 logicLennart Poettering2023-03-011-1/+18
|
* machined: add support for memory pressure + SIGRTMIN+18Lennart Poettering2023-03-011-1/+11
|
* journald: hook up journald with the memory pressure and SIGRTMIN+18 logicLennart Poettering2023-03-014-2/+56
|
* resolved: flush caches on memory pressure and support SIGRTMIN+18Lennart Poettering2023-03-013-1/+36
|
* shared: add a common SIGRTMIN-18 handlerLennart Poettering2023-03-013-0/+153
|
* pam_systemd: process the two new capabilities user records fields in pam_systemdLennart Poettering2023-02-281-13/+135
| | | | | | | | | | | | | | | | | | | And also: by default, for the systemd-user service and for local sessions (i.e. those assigned to a seat): let's imply CAP_WAKE_SYSTEM for them by default. Yes, let's pass one specific capability by default to local unprivileged users. The capability services exactly once purpose: to allow system wake-up from suspend via alarm clocks, hence is relatively limited in focus. By adding this tools such as GNOME's Alarm Clock app can simply allocate a CLOCK_REALTIME_ALARM (or ask systemd --user to do this) timer and it will wake up the system as necessary. Note that systemd --user will not pass the ambient caps on by default, so even with this change, individual services need to use AmbientCapabilities= to pass this on to the individual programs. Fixes: #17564 #21382
* homectl: make the new caps field configurable via homectlLennart Poettering2023-02-281-1/+68
|
* user-record: extend user records with an ambient and bounding caps set fieldLennart Poettering2023-02-283-0/+66
| | | | | In particular the ambieht caps field is useful: we can use it later to pass caps such as CAP_WAKE_ALARM to regular users on login.
* boot: Provide div0 handlers for ARMJan Janssen2023-02-282-8/+20
| | | | This is a cleaner approach to 59833064742310bfccf028b0278811ba5cff8dcf.
* boot: Fix data model detection for ARMJan Janssen2023-02-281-1/+1
| | | | For whatever reason, ARM does not define __ILP32__.
* psi-util: fix error handlingLennart Poettering2023-02-281-9/+15
| | | | | | | We checked ERRNO_IS_NOT_SUPPORTED on a possible positive non-error code, which isn't right. Fix that. Also add caching, since we are about to call this more often.
* sd-event: handle kernels that set CONFIG_PSI_DEFAULT_DISABLED more gracefullyLennart Poettering2023-02-281-2/+11
| | | | | | | If CONFIG_PSI_DEFAULT_DISABLED is set in the kernel, then the PSI files will be there, and you can open them, but read()/write() will fail. Which is terrible, since that happens so late. But anyway, handle this gracefully.
* journald: remove triplicate logging about failure to write log linesLennart Poettering2023-02-281-11/+7
| | | | | | | | | | | | | | | | | | | Let's log exactly at one place about failed writing of log lines to journal file: in shall_try_append_again(). Then, if we decide to suppress a retry-after-vacuum because we already vacuumed anyway then say this explicitly as "supressed rotation", because that's what we do here. This removes triplicate logging about the same error, and logs exactly once, plus optional one "suppressed rotation" message. (plus more debug output). The triplicate logging was bad in particular because it had no understanding of the actual error codes and just showed generic UNIX error strings ("Not a XENIX named type file"). By relying on shall_try_append_again() to do all logging we now get very clean error strings for all conditions. Fixes: #26496
* journald: always pass error code to logging function, even if we don't use ↵Lennart Poettering2023-02-281-13/+13
| | | | | | | | it with %m We always want to pass the error code along with the log call, so that it can add it to structured logging, even if the format string does not contain %m.
* journald: upgrade log message about missing mmap() support to LOG_ERRLennart Poettering2023-02-281-1/+1
| | | | | in this case we really cannot proceed and fail. Let's log about this loudly, since we simply fail the operation to write anything.
* journald: downgrade various log messages from LOG_WARNING to LOG_INFOLennart Poettering2023-02-281-6/+6
| | | | | | | | | | | | | None of these conditions are real issues, but they can simply happen because we just swtched from /run to /var as backend for logging and there are old files from different boots with different systemd versions and so on. Let's not make more noise than necessary: still log, but not consider it a warning, but just some normal thing. We are handling these issues safely after all: by rotating and starting anew, i.e. there's no reason to be concerned.
* journald: start log message uppercase, like every other one aroundLennart Poettering2023-02-281-1/+1
|
* journald: make sure shall_try_append_again() logs about all return codes ↵Lennart Poettering2023-02-281-0/+1
| | | | passed in, not just some
* systemctl: print better message if default target is maskedDavid Tardon2023-02-272-0/+4
| | | | | | | | | | | If the default target is masked, `systemctl get-default` prints Failed to get default target: Operation not possible due to RF-kill That's a bit too cryptic, so let's make it clear what's actually happening. Fixes #26589.
* tests: temporarily disable time-util failing testsLuca Boccassi2023-02-271-2/+3
| | | | | These are failing since https://github.com/systemd/systemd/pull/26409 disable for now
* Revert "dissect-image: don't probe swap partitions needlessly"Lennart Poettering2023-02-271-1/+4
| | | | | | | | | | | | This reverts commit df4524cb3796529b435af309f5e6a2d92bcdaaa0. This commit is just wrong. The thing is that we *don't* know automatically that the partition contains a swap image, because it could be encrypted. Hence revert. Fixes: #26595
* Merge pull request #26578 from thkukuk/mainYu Watanabe2023-02-253-0/+34
|\ | | | | sd-login: add sd_uid_get_login_time interface #26574
| * sd-login: add sd_uid_get_login_time interface #26574Thorsten Kukuk2023-02-253-0/+34
| |
* | tpm2-util: use compound initialization when allocating tpm2 objectsLennart Poettering2023-02-241-5/+9
| |
* | tree-wide: Use correct SPDX license identifierJan Janssen2023-02-243-3/+3
| |
* | Merge pull request #26579 from poettering/manager-env-clean-upLennart Poettering2023-02-241-7/+15
|\ \ | | | | | | service manager env var clean-up fixes
| * | manager: be more careful with env var clean-upLennart Poettering2023-02-241-7/+15
| |/ | | | | | | | | Let's add some more env vars we nowadays set for activated services to the list of env vars we strip from the environment block we pass on.
* | mempool: fix tile alignment checkLennart Poettering2023-02-241-2/+4
| | | | | | | | | | | | | | | | | | | | We should check alignment *after* determining the pointer points into our pool, not before. Otherwise might might end up checking alignment of the pointer relative to our base, even though it is taken relative to some other base. Follow-up for: a2b052b29f8bc141e94a4af95d1653a38a57eaeb See: https://github.com/systemd/systemd/pull/26393#issuecomment-1442295012
* | libsystemd: sd_journal_get_seqnum() must be tagged with 254 symver, not 253Lennart Poettering2023-02-241-1/+1
| | | | | | | | | | | | This is a follow-up for b1712fabd1702640b04b0acdbba2d78294313a4d which was prepped for 253, but merged into early 254 development cycle. It thus had the symbol it adds at the wrong symver. Fix thta.
* | Merge pull request #26409 from yuwata/parse-timestampLuca Boccassi2023-02-243-172/+592
|\ \ | | | | | | fix parse_timestamp()
| * | test: add tests for format_timestamp() and parse_timestamp() with various ↵Yu Watanabe2023-02-241-12/+366
| | | | | | | | | | | | timezone
| * | time-util: make parse_timestamp() use the RFC-822/ISO 8601 standard timezone ↵Yu Watanabe2023-02-241-62/+112
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | spec If the timezone is specified with a number e.g. +0900 or so, then let's parse the time as a UTC, and adjust it with the specified time shift. Otherwise, if an area has timezone change, e.g. --- Africa/Casablanca Sun Jun 17 01:59:59 2018 UT = Sun Jun 17 01:59:59 2018 +00 isdst=0 gmtoff=0 Africa/Casablanca Sun Jun 17 02:00:00 2018 UT = Sun Jun 17 03:00:00 2018 +01 isdst=1 gmtoff=3600 Africa/Casablanca Sun Oct 28 01:59:59 2018 UT = Sun Oct 28 02:59:59 2018 +01 isdst=1 gmtoff=3600 Africa/Casablanca Sun Oct 28 02:00:00 2018 UT = Sun Oct 28 03:00:00 2018 +01 isdst=0 gmtoff=3600 --- then we could not determine isdst from the timezone (+01 in the above) and mktime() will provide wrong results. Fixes #26370.
| * | time-util: drop unnecessary assignment of timezone nameYu Watanabe2023-02-241-4/+1
| | | | | | | | | | | | As mktime() does not use timezone neme.
| * | time-util: rename variablesYu Watanabe2023-02-241-9/+9
| | | | | | | | | | | | No functional changes, just refactoring.
| * | time-util: shorten code a bitYu Watanabe2023-02-241-16/+9
| | | | | | | | | | | | No functional change, just refactoring.
| * | time-util: use usec_add() and usec_sub_unsigned()Yu Watanabe2023-02-241-10/+7
| | | | | | | | | | | | | | | And move the check with USEC_TIMESTAMP_FORMATTABLE_MAX at the end, as usec_add() can handle overflow correctly.
| * | time-util: use result from startswith_no_case()Yu Watanabe2023-02-241-10/+4
| | | | | | | | | | | | No functional change, just refactoring.
| * | time-util: do not use strdupa()Yu Watanabe2023-02-241-4/+12
| | | | | | | | | | | | The input string may come from command line, config files.
| * | time-util: drop redundant elseYu Watanabe2023-02-241-4/+7
| | |
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 09:40:40 +0100