summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* hwdb: Force "mouse" type on Logitech Ultrathin Touch Mousewip/hadess/logitech-ultrathin-touch-mouseBastien Nocera2020-05-051-0/+4
| | | | Closes: #15657
* Merge pull request #15645 from poettering/calender-expression-doc-fixZbigniew Jędrzejewski-Szmek2020-05-054-18/+35
|\ | | | | some calendar expression fixes and documentation updates
| * man: expand on the star…end/repetition time expressionsLennart Poettering2020-05-051-9/+8
| | | | | | | | | | | | | | And attempt to explain what is requested in #15030, but still be concise. Fixes: #15030
| * calendarspec: be more graceful with two kinds of calendar expressionsLennart Poettering2020-05-052-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changes the calendarspec parser to allow expressions such as "00:05..05", i.e. a range where start and end is the same. It also allows expressions such as "00:1-2/3", i.e. where the repetition value does not fit even once in the specified range. With this patch both cases will now be optimized away, i.e. the range is removed and a fixed value is used, which is functionally equivalent. See #15030 for an issue where the inability to parse such expressions caused confusion. I think it's probably better to accept these gracefully and optimizing them away instead of refusing them with a plain EINVAL. With a tool such as "systemd-analyze" calendar it should be easy to figure out the normalized form with the redundant bits optimized away.
| * calendarspec: minor simplificationLennart Poettering2020-05-051-3/+2
| |
| * calendarspec: drop _pure_ from static functionLennart Poettering2020-05-051-1/+1
| | | | | | | | | | For static functions the compiler should be able to determine this on its own, let's not add needless decorators.
| * calendarspec: pack our flags a bitLennart Poettering2020-05-051-3/+3
| |
| * calendarspec: encode that it's OK to store µs in 'int'sLennart Poettering2020-05-051-0/+3
| |
* | Revert "logs-show: declare [static 2] on all highlight parameters"Frantisek Sumsal2020-05-052-10/+10
| | | | | | | | | | | | This reverts commit 5444520628830aacab85be630a6cdeb179ff510b. See: https://github.com/systemd/systemd/pull/15706
* | Merge pull request #15648 from poettering/journalctl-cat-beefupZbigniew Jędrzejewski-Szmek2020-05-053-44/+72
|\ \ | | | | | | journalctl: honour --output-fields= in -o cat mode
| * | logs-show: declare [static 2] on all highlight parametersLennart Poettering2020-05-052-10/+10
| | |
| * | man: document the new -o cat featureLennart Poettering2020-05-051-7/+9
| | |
| * | journalctl: optionally, show a different field than MESSAGE in -o cat modeLennart Poettering2020-05-051-27/+53
| | | | | | | | | | | | Fixes: #15621
| * | journal: use set_contains() where appropriateLennart Poettering2020-05-051-1/+1
| | |
* | | man: migrate more specifier explanations to standard-specifiers.xmlLennart Poettering2020-05-055-90/+45
| | | | | | | | | | | | | | | | | | | | | We probably can migrate even more, but for now let's just migrate those which have the 1:1 identical text everywhere. (Also, let's add the % entry to all specifier tables)
* | | Merge pull request #15701 from poettering/systemctl-json-tableZbigniew Jędrzejewski-Szmek2020-05-052-16/+70
|\ \ \ | | | | | | | | systemctl: optionally output tables as json
| * | | systemctl: optionally output tables in JSON formatLennart Poettering2020-05-051-10/+30
| | | |
| * | | format-table: generate better JSON field namesLennart Poettering2020-05-051-6/+40
| | |/ | |/| | | | | | | | | | | | | | | | Let's try to mangle table contents a bit to make them more suitable as JSON field names. Specifically when we see "foo bar" convert this to "foo_bar" as field name, as variable/field names are generally assumed to be without spaces.
* | | correct evdev dimensions for T490 trackpadianhi2020-05-051-4/+4
| | | | | | | | | | | | | | | | | | The original source of these dimensions had swapped the x y dimension arguments to touchpad-edge-detector. The correct dimensions are x = 100 mm, y = 68 mm
* | | hwdb: Fix brightness keys for Logitech K811Diego Escalante Urrelo2020-05-051-0/+5
| | | | | | | | | | | | Closes: #15698
* | | shutdown: fix spacing in shutdown error messageLennart Poettering2020-05-051-1/+1
| |/ |/|
* | nspawn: mount custom paths before writing to /etcMotiejus Jakštys2020-05-051-10/+10
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Consider such configuration: $ systemd-nspawn --read-only --timezone=copy --resolv-conf=copy-host \ --overlay="+/etc::/etc" <...> Assuming one wants `/` to be read-only, DNS and `/etc/localtime` to work. One way to do it is to create an overlay filesystem in `/etc/`. However, systemd-nspawn tries to create `/etc/resolv.conf` and `/etc/localtime` before mounting the custom paths, while `/` (and, by extension, `/etc`) is read-only. Thus it fails to create those files. Mounting custom paths before modifying anything in `/etc/` makes this possible. Full example: ``` $ debootstrap buster /var/lib/machines/t1 http://deb.debian.org/debian $ systemd-nspawn --private-users=false --timezone=copy --resolv-conf=copy-host --read-only --tmpfs=/var --tmpfs=/run --overlay="+/etc::/etc" -D /var/lib/machines/t1 ping -c 1 example.com Spawning container t1 on /var/lib/machines/t1. Press ^] three times within 1s to kill container. ping: example.com: Temporary failure in name resolution Container t1 failed with error code 130. ``` With the patch: ``` $ sudo ./build/systemd-nspawn --private-users=false --timezone=copy --resolv-conf=copy-host --read-only --tmpfs=/var --tmpfs=/run --overlay="+/etc::/etc" -D /var/lib/machines/t1 ping -qc 1 example.com Spawning container t1 on /var/lib/machines/t1. Press ^] three times within 1s to kill container. PING example.com (93.184.216.34) 56(84) bytes of data. --- example.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 110.912/110.912/110.912/0.000 ms Container t1 exited successfully. ```
* Merge pull request #15636 from poettering/sensitivity-trainingAnita Zhang2020-05-045-2/+45
|\ | | | | be more careful when setting json variant + dbus message sensitive flag
| * home: make sure whenever we touch the 'secret' part of a user record, we set ↵Lennart Poettering2020-04-291-1/+8
| | | | | | | | the the sensitive flag on it
| * home: mark various bus messages we write user records to as sensitiveLennart Poettering2020-04-292-0/+6
| | | | | | | | | | let's make sure that when we append potentially sensitive data to a bus message we set the sensitive flag on the message object.
| * json: when making a copy of a json variant, propagate the sensitive bitLennart Poettering2020-04-292-1/+31
| | | | | | | | | | Let's make sure we never lose the bit when copying a variant, after all the data contained is still going to be sensitive after the copy.
* | Merge pull request #15647 from benzea/benzea/graphical-use-app-prefixAnita Zhang2020-05-041-9/+9
|\ \ | | | | | | docs: Change prefix for desktop applications to app-
| * | docs: Change prefix for desktop applications to app-Benjamin Berg2020-04-301-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need both a slice name and a prefix for application units. For consistency we tried to use the same name and ended up standardising on "apps.slice" and and "apps-" prefix for the units. However, "app-" would be a more natural prefix for applications. And it is no problem to simply also name the slice "app.slice" for consistency rather than keeping the current "apps.slice".
* | | mkosi: Fix openSUSE image declarationMichal Koutný2020-05-041-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | User accounts of given names are necessary for the build script and tests to succeed. (Fixup of #15527, too keen cleaning of dependencies and cached image caused this.)
* | | Add Kensington SlimBlade TrackballLukas Klingsbo2020-05-041-0/+4
| | |
* | | catalog,po: update Polish translationPiotr Drąg2020-05-042-10/+40
| | |
* | | test: fix potential use-after-freeFrantisek Sumsal2020-05-041-1/+1
| | | | | | | | | | | | CID#1428676.
* | | Merge pull request #15422 from nolange/add_zstd_coredumpEvgeny Vereshchagin2020-05-0416-59/+357
|\ \ \ | | | | | | | | coredump: add zstandard support for coredumps
| * | | install libzstd-dev for CI buildsNorbert Lange2020-05-045-1/+10
| | | |
| * | | coredump: add zstandard support for coredumpsNorbert Lange2020-05-0411-58/+347
| | | | | | | | | | | | | | | | | | | | this will hook libzstd into coredump, using this format as default.
* | | | basic: add STRCASE_IN_SET() which is to STR_IN_SET() what strcaseeq() is to ↵Lennart Poettering2020-05-045-19/+60
|/ / / | | | | | | | | | streq()
* | | man: fix few spelling errorsFrantisek Sumsal2020-05-033-3/+3
| | | | | | | | | | | | Reported by Fossies.org.
* | | test: Fix build with !HAVE_LZ4 && HAVE_XZMichal Koutný2020-05-021-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | HUGE_SIZE was defined inconsistently. > In file included from ../src/basic/alloc-util.h:9, > from ../src/journal/test-compress.c:9: > ../src/journal/test-compress.c: In function ‘main’: > ../src/journal/test-compress.c:280:33: error: ‘HUGE_SIZE’ undeclared (first use in this function) > 280 | assert_se(huge = malloc(HUGE_SIZE));
* | | cifuzz: upload artifacts only when the "run fuzzers" step failsEvgeny Vereshchagin2020-05-021-1/+2
| | |
* | | repart: fix partition maximum size segfaultEmmanuel Garette2020-05-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Discovered, tracked down and fix proposed by Emmanuel Garette. See: https://lists.freedesktop.org/archives/systemd-devel/2020-April/044435.html (Lennart turned this into a PR) Fixes: #15608
* | | Merge pull request #15652 from MadMcCrow/masterZbigniew Jędrzejewski-Szmek2020-05-011-0/+4
|\ \ \ | | | | | | | | Fix Chromebook Caroline board accelerometer not having correct orientation
| * | | Fix Chromebook Caroline board accelerometer not having correct orientationMadMcCrow2020-04-301-0/+4
| | | |
* | | | Merge pull request #15547 from kkdwivedi/notify-barrierLennart Poettering2020-05-019-12/+163
|\ \ \ \ | | | | | | | | | | Introduce sd_notify_barrier
| * | | | man: sd_notify() race is gone with sd_notify_barrier()Kumar Kartikeya Dwivedi2020-05-013-11/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add note for change of behaviour in systemd-notify, where parent pid trick is only used when --no-block is passed, and with enough privileges ofcourse. Also, fix a small error in systemd(1).
| * | | | Introduce sd_notify_barrierKumar Kartikeya Dwivedi2020-05-016-1/+130
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds the sd_notify_barrier function, to allow users to synchronize against the reception of sd_notify(3) status messages. It acts as a synchronization point, and a successful return gurantees that all previous messages have been consumed by the manager. This can be used to eliminate race conditions where the sending process exits too early for systemd to associate its PID to a cgroup and attribute the status message to a unit correctly. systemd-notify now uses this function for proper notification delivery and be useful for NotifyAccess=all units again in user mode, or in cases where it doesn't have a control process as parent. Fixes: #2739
* | | | | Merge pull request #13512 from msekletar/freezerZbigniew Jędrzejewski-Szmek2020-05-0127-24/+926
|\ \ \ \ \ | |/ / / / |/| | | | core: introduce support for cgroup freezer
| * | | | test: add test for cgroup v2 freezer supportMichal Sekletár2020-04-306-0/+310
| | | | |
| * | | | core: introduce support for cgroup freezerMichal Sekletár2020-04-3019-14/+566
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With cgroup v2 the cgroup freezer is implemented as a cgroup attribute called cgroup.freeze. cgroup can be frozen by writing "1" to the file and kernel will send us a notification through "cgroup.events" after the operation is finished and processes in the cgroup entered quiescent state, i.e. they are not scheduled to run. Writing "0" to the attribute file does the inverse and process execution is resumed. This commit exposes above low-level functionality through systemd's DBus API. Each unit type must provide specialized implementation for these methods, otherwise, we return an error. So far only service, scope, and slice unit types provide the support. It is possible to check if a given unit has the support using CanFreeze() DBus property. Note that DBus API has a synchronous behavior and we dispatch the reply to freeze/thaw requests only after the kernel has notified us that requested operation was completed.
| * | | | basic/cgroup-util: introduce cg_get_keyed_attribute_full()Michal Sekletár2020-04-293-4/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Callers of cg_get_keyed_attribute_full() can now specify via the flag whether the missing keyes in cgroup attribute file are OK or not. Also the wrappers for both strict and graceful version are provided.
| * | | | selinux: do preprocessor check only in selinux-access.cMichal Sekletár2020-04-291-9/+0
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | This has the advantage that mac_selinux_access_check() can be used as a function in all contexts. For example, parameters passed to it won't be reported as unused if the "function" call is replaced with 0 on SELinux disabled builds.
View Lorry Controller Status