3151a11061
TODO: add entry
2018-11-16 19:47:07 +01:00
aac99f303a
core: introduce a helper function to wrap unit_log_{success,failure}
...
It's inline so that the compiler can easily optimize away the call to get
status string.
2018-11-16 19:47:07 +01:00
14c4da2ffe
Merge pull request #10805 from poettering/migrate-boot-loader-interface
...
migrate boot loader interface doc from wiki into markdown (split out of #10495 )
2018-11-16 17:55:08 +01:00
464e48f495
Merge pull request #10751 from yuwata/sd-event-util
...
Reuse sd_event_source object for timer event
2018-11-16 17:54:43 +01:00
ae3cc6ec0d
Merge pull request #10770 from poettering/unit-done-log
...
improvements to structure log events from PID1
2018-11-16 17:54:19 +01:00
ca0e33734e
Merge pull request #10777 from poettering/seccomp-filter-others
...
list syscalls supported by the local kernel but not in any syscall groups explicitly in "systemd-analyze syscall-filter"
2018-11-16 17:53:50 +01:00
6415fecd4c
Merge pull request #10785 from poettering/cgroup-join-removal
...
remove JoinControllers= setting
2018-11-16 17:53:26 +01:00
3382cf28b6
Merge pull request #10802 from poettering/hide-only-on
...
man: let's deprecate PermissionsStartOnly=
2018-11-16 17:53:01 +01:00
1b259a5bf3
Merge pull request #10804 from poettering/sd-boot-updates
...
various sd-boot/EFI fixes (split out from #10495 )
2018-11-16 17:52:37 +01:00
db0ba2a4a4
Merge pull request #10806 from poettering/logind-many-fixes
...
various smaller fixes and improvements to logind (split out of #10495 )
2018-11-16 17:52:11 +01:00
6fdc4831bb
docs: tweak index.md generation and run it again
2018-11-16 17:44:27 +01:00
2fe8213230
docs: migrate boot loader interface from fdo wiki to git
...
This imports
https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface/
into our sources, and extends it substantially with various variables
now supported.
2018-11-16 17:43:59 +01:00
2640b77356
docs/TRANSIENT-SETTINGS: drop PermissionsStartOnly= from
2018-11-16 16:21:21 +01:00
a9bfb3eff2
analyze: add some minimal ANSI highlighting of syscall-filter output
2018-11-16 16:10:57 +01:00
a05cfe230f
seccomp: add some missing syscalls to filter sets
2018-11-16 16:10:57 +01:00
cdf6258c2e
analyze: show list of syscalls the kernel supports but not included in any group in the output
...
This is quite useful for making sure our list is complete.
2018-11-16 16:10:57 +01:00
f20db19954
cocci: simplify some if checks
2018-11-16 16:05:29 +01:00
0c093a62ef
logind: fix determination of CanHibernate() and other calls
...
As suggest here:
https://github.com/systemd/systemd/issues/10250#issuecomment-426788301
Fixes : #10250
(This suggested patch has been converted into a proper commit by me,
Lennart, with attribution to the original author, @henryptung)
2018-11-16 15:52:22 +01:00
c78e6f9e7b
logind: imply right to reboot when user has right to set reboot-to-firmware flag
...
Let's reduce the number of actions the user has to acquire.
2018-11-16 15:52:22 +01:00
68d7c268f8
efivars: let's add some validation of boot menu entry name syntax
2018-11-16 15:52:22 +01:00
cea72d53f8
efivars: add new helper efi_set_variable_string()
...
Let's make it easier to parse an UTF-16 string properly.
2018-11-16 15:52:22 +01:00
c57ed5735f
logind: log correct error msg
2018-11-16 15:52:22 +01:00
75100aeb9f
logind: sort includes
2018-11-16 15:52:22 +01:00
80641a81b6
bootctl: display loader features in a pretty way.
2018-11-16 15:52:22 +01:00
c027b67f53
util: force time multiplications to happen in longs
2018-11-16 15:52:22 +01:00
52ecf1958d
locale-util: add special glyph support for check marks/cross marks
2018-11-16 15:52:22 +01:00
3b42f34910
efi: NUL terminate strings read with efivar_get()
...
let's be more careful and NUL terminate everything we read from EFI
variables, in case it isn't already.
2018-11-16 15:47:18 +01:00
996daf2fa9
sd-boot: make sure special menu items also work if menu is skipped
...
While it doesn't really make much sense to set "auto-reboot-to-firmware"
as oneshot boot item, let's still support it properly, by also
dispatching such a menu item if selected.
2018-11-16 15:47:18 +01:00
aec1443aec
sd-boot: use structured initialization
2018-11-16 15:47:18 +01:00
b58c7351c0
sd-boot: change name of automatic entry for rebooting into firmware
...
Let's stick to one nomenclature. In userspace we usually call this
"reboot to firmware setup", hence use the same name in sd-boot too.
This name was previously only relevant internally, but since the
addition of the LoaderEntries EFI var is exposed to userspace, hence
let's get this right with the first release adding this.
2018-11-16 15:47:18 +01:00
5dd5f7cfa8
sd-boot: add new EFI variable exposing feature set of boot loader
...
We keep adding new features, let's advertise to the host OS what these
are in a new variable LoaderFeatures.
It works a bit like OsIndicationsSupported, but is about Loader
features.
2018-11-16 15:47:18 +01:00
95a18e91db
efi: make sure parse_boolean() does something useful on a NULL parameter
2018-11-16 15:47:18 +01:00
427ee7ec82
efi: add 'const' to various util.h API parameters
2018-11-16 15:47:18 +01:00
fe2579dd9c
sd-boot: introduce a one-time override for the boot menu timeout
...
This is useful to allow userspace to request a "boot into boot menu"
feature.
2018-11-16 15:47:18 +01:00
2366d92345
sd-boot: when converting menu timeout for UINTN to INTN saturate
...
Let's be a bit more careful and handle overly long timeouts in a
slightly more sensible way.
2018-11-16 15:47:18 +01:00
b49dd00f8c
efi: add simple macros for MAX values of EFI's UINTN/INTN types
2018-11-16 15:47:18 +01:00
8ac694710f
sd-boot: timeout_sec is unsigned hence show it with %u
2018-11-16 15:47:18 +01:00
4e96eb682c
logind: also expose bool prop on bus that declares whether we are on external power
...
The three core variables that affect idleness handling are whether we
are docked, whether we are on AC power and whether the lid is closed,
hence let's also expose the third variable on the bus, to make things
nicely debuggable.
2018-11-16 15:39:31 +01:00
e455380b18
logind: make sure that if we can't figure out whether we are on AC we presume we are
...
It's safer to assume that we are on AC than to assume we are on battery,
if we can't figure it out.
2018-11-16 15:39:31 +01:00
c30e0d7b6a
logind: don't claim that RebootToFirmwareSetup was constant
...
It's not, after all, that's what SetRebootToFirmware() is about.
(I was wondering for a moment whether to make this EMITS_CHANGES, but
decided against it, given that the flag actually can be changed
externally to logind too, and we couldn't send out notifications for
that.)
2018-11-16 15:39:31 +01:00
9b9c23daf4
logind: expose a boolean on the bus explaining whether logind thinks the lid is closed
...
This copies how we already expose a "Docked" boolean the reflects
whether we are in a docking station or not.
2018-11-16 15:39:31 +01:00
ff30a86bd4
job: simplify status message extraction
...
As @keszybz points out these fields are always here, there's no point in
checking if they are NULL or not.
2018-11-16 15:30:36 +01:00
9a80f2f453
job: when a job was skipped due to a failed condition, log about it
...
Previously we'd neither show console status output nor log output. Let's
fix that, and still log something.
2018-11-16 15:30:36 +01:00
6e64994d69
core: make unit_start() return a distinguishable error code in case conditions didn't hold
...
Ideally we'd even propagate this all the way to the client, by having a
separate JobType enum value for this. But it's hard to add this without
breaking compat, hence for now let's at least internally propagate this
case differently from the case "already on it".
This is then used to call job_finish_and_invalidate() slightly
differently, with the already= parameter false, as in the failed
condition case no message was likely produced so far.
2018-11-16 15:22:48 +01:00
0e2b4a822e
job: add two explanatory comments
2018-11-16 15:22:48 +01:00
a69b3872ac
job: let's remove one comparison and reduce indentation level by one
2018-11-16 15:22:48 +01:00
523ee2d414
core: log a recognizable message when a unit succeeds, too
...
We already are doing it on failure, let's do it on success, too.
Fixes : #10265
2018-11-16 15:22:48 +01:00
91bbd9b796
core: make log messages about unit processes exiting recognizable
2018-11-16 15:22:48 +01:00
7c047d7443
core: make log messages about units entering a 'failed' state recognizable
...
Let's make this recognizable, and carry result information in a
structure fashion.
2018-11-16 15:22:48 +01:00
295f31b0b7
sd-messages: add comment and reorder a bit
...
The message SD_MESSAGE_UNIT_FAILED is closely related to
SD_MESSAGE_UNIT_STARTED as it is generated when a start job failed
instead of completed successfully, Hence they should be placed together.
Otherwise one might get the impression that the message was about
failing units, which it really is not.
2018-11-16 15:22:48 +01:00
Zbigniew Jędrzejewski-Szmek