| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
| |
We usually seperate case statements within a switch from each other by
empty lines. We also often add an empty line after multi-line function
prototypes, let's do so here too
Also, no trailing ; after }...
|
|
|
|
| |
--dump-configuration-items output
|
|\
| |
| | |
add new specifiers %T and %V that expand to /tmp or /var/tmp or $TMP/$TMPDIR/$TEMP
|
| | |
|
| |
| |
| |
| | |
system-tmpfiles is not a "service manager" hence say "command" instead.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This corresponds nicely with the specifiers we already pass for
/var/lib, /var/cache, /run and so on.
This is particular useful to update the test-path service files to
operate without guessable files, thus allowing multiple parallel
test-path invocations to pass without issues (the idea is to set $TMPDIR
early on in the test to some private directory, and then only use the
new %T or %V specifier to refer to it).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Usually, we order our settings in our unit files in a logical order,
grouping related settings together, and putting more relevant stuff
first, instead of following a strictly alphabetical order.
For specifiers I think it makes sense to follow an alphabetical order
however, since they literally are just characters, and hence I think the
concept of alphabetical ordering is much more commanding for them. Also,
since specifiers are usually not used in combination, but mostly used
indepdently of each other I think it's not that important to group
similar ones together.
No other changes except the reordering.
|
|\ \
| |/
|/| |
core: make StateDirectory= or friends works with DynamicUser= and RootDirectory=/RootImage=
|
| |
| |
| |
| |
| |
| |
| | |
friends are set
The directories specified by RuntimeDirectory= or friends are created
on host. So, it is necessary to bind-mount them on root directory.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
RootDirectory=/RootImage=
The symbolic links to private directories specified by StateDirectory=
or its friends are created on the host. So, when DynamicUser= and
RootDirectory=/RootImage= are set, then the executed process cannot
access private directory.
This makes the private directories are mounted on the non-private place
when both DynamicUser= and RootDirectory=/RootImage= are set.
Fixes #8965.
|
| |
| |
| |
| | |
Follow-up for #8817.
|
|\ \
| | |
| | | |
More tables tests
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This makes it easier to link the nspawn implementation to the tests.
Right now this just means that nspawn-patch-uid.c is not compiled
twice, which is nice, but results in test-patch-uid being slightly bigger,
which is not nice. But in general, we should use convenience libs to
compile everything just once, as far as possible. Otherwise, once we
start compiling a few files here twice, and a few file there thrice, we
soon end up in a state where we are doing hundreds of extra compilations.
So let's do the "right" thing, even if is might not be more efficient.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Nspawn umask
|
| | | |
| | | |
| | | |
| | | | |
Fixes #8911.
|
| |/ /
| | |
| | |
| | |
| | | |
Sometimes an empty line is good for readability, but here I think
they all can be removed without any loss.
|
| | |
| | |
| | |
| | | |
They all pass fine, but let's keep testing regularly.
|
|\ \ \
| |/ /
|/| | |
completion: fixes for `systemctl status --property`
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Fixes #9041.
|
| | |
| | |
| | |
| | | |
'systemctl -p'
|
| | |
| | |
| | |
| | |
| | |
| | | |
'systemctl -p'
Closes #5137.
|
| | |
| | |
| | |
| | |
| | | |
If systemd is invoked with this option, this dumps all bus properties.
This may be useful for shell completion for `systemctl --property`.
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
sd-bus: use _cleanup_ more
|
| | |
| | |
| | |
| | | |
Noticed by Craig Barnes.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Fixes #9089.
|
|/ /
| |
| |
| | |
Closes #9086.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When dealing with a large number of template instances, for example
when launching daemons per VRF, it is hard for operators to correlate
log lines to arguments.
Add a new with-unit mode which, if available, prefixes unit and user
unit names when displaying its log messages instead of the syslog
identifier. It will also use the full timestamp with timezones, like
the short-full mode.
|
| |
| |
| |
| | |
Follow-ups for #8620.
|
|\ \
| |/
|/| |
an implementation of the "portable services" concept
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds a small service "systemd-portabled" and a matching client
"portablectl", which implement the "portable service" concept.
The daemon implements the actual operations, is PolicyKit-enabled and is
activated on demand with exit-on-idle.
Both the daemon and the client are an optional build artifact, enabled
by default rhough.
|
| |
| |
| |
| | |
This way, we can reuse it in portabled.
|
| |
| |
| |
| |
| | |
Much like the previous commit, but for Image objects rather than Machine
objects.
|
| |
| |
| |
| |
| |
| |
| |
| | |
from manager to machine object
Let's shorten the code a bit, and unify how we forward executoin from
the machine functions that take a machine name as first argument to the
matching functions on the machine object.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds directories in /etc and /run to the search paths for OS
images. While it doesn't make much sense to actually place huge disk
images there, it's good enough for symlinks to those.
The main reason for supporting this is that this allows us to neatly
symlink portable image files located outside of the search path into the
search path when attaching them, so that attaching them also means they
are discoverable properly for all commands.
|