| Age | Commit message (Collapse) | Author |
|---|
|
|
|
In order to re-use the policy definitions, factor them out into their own
files.
|
|
When this system-wide start-up timeout is hit we execute one of the
failure actions already implemented for services that fail.
This should not only be useful on embedded devices, but also on laptops
which have the power-button reachable when the lid is closed. This
devices, when in a backpack might get powered on by accident due to the
easily reachable power button. We want to make sure that the system
turns itself off if it starts up due this after a while.
When the system manages to fully start-up logind will suspend the
machine by default if the lid is closed. However, in some cases we don't
even get as far as logind, and the boot hangs much earlier, for example
because we ask for a LUKS password that nobody ever enters.
Yeah, this is a real-life problem on my Yoga 13, which has one of those
easily accessible power buttons, even if the device is closed.
|
|
|
|
They are unused and unlikely to ever be.
|
|
One missing string found.
A few things had to be moved around to make it possible to test them.
|
|
It's used for the FailureAction property as well.
|
|
|
|
Jan: test-tables fails on my system. The one it's failing on is:
syscall: 222 → (null) → -1
... and indeed, our own tables should not have holes, but syscall
tables certainly might.
|
|
|
|
The tests check if the tables have entries for all values
in the enum, and that the entries are unique.
|
