| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
They do not use any functions from libcap directly. The CAP_KILL constant in
use by these files comes from <linux/capability.h> imported through
"missing.h".
Tested that "systemd-machined" builds cleanly and works after this change.
|
| |
|
|
| |
This way "machinectl login" can be opened up to run without privileges.
|
| |
|
|
|
|
|
| |
on a pty and returns the pty master fd to the client
This is a one-stop solution for "machinectl login", and should simplify
getting logins in containers.
|
| |
|
|
| |
For that, ask machined for a container PTY and use that.
|
| |
|
|
|
|
| |
container
Then, port "machinectl" over to make use of it.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This adds a new bus call to machined that enumerates /var/lib/container
and returns all trees stored in it, distuingishing three types:
- GPT disk images, which are files suffixed with ".gpt"
- directory trees
- btrfs subvolumes
|
| | |
|
| |
|
|
|
|
| |
src/libsystemd/sd-bus/bus-common-errors.h
Stuff in src/shared/ should not use stuff from src/libsystemd/ really.
|
| |
|
|
| |
account
|
| |
|
|
|
|
|
| |
In the long run this should become a full fledged client to networkd
(but not before networkd learns bus support). For now, just pull
interesting data out of networkd, udev, and rtnl and present it to the
user, in a simple but useful output.
|
| |
|
|
|
|
|
|
| |
Let's settle on a single type for all address family values, even if
UNIX is very inconsitent on the precise type otherwise. Given that
socket() is the primary entrypoint for the sockets API, and that uses
"int", and "int" is relatively simple and generic, we settle on "int"
for this.
|
| |
|
|
|
| |
We mostly use "family" to refer to AF_INET, AF_INET6, etc, let's use
this terminology here, too
|
| |
|
|
| |
with containers
|
| |
|
|
| |
nss-myhostname uses
|
| |
|
|
|
|
|
| |
private in-addr-util.[ch]
These are enough calls for a new file, and they are sufficiently
different from the sockaddr-related calls, hence let's split this out.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
attached to a bus connection
This makes callback behaviour more like sd-event or sd-resolve, and
creates proper object for unregistering callbacks.
Taking the refernce to the slot is optional. If not taken life time of
the slot will be bound to the underlying bus object (or in the case of
an async call until the reply has been recieved).
|
| |
|
|
|
|
|
|
|
|
|
| |
sd_bus_path_{encode,decode}()
The new calls work similarly, but enforce a that a common, fixed bus
path prefix is used.
This follows discussions with Simon McVittie on IRC that it should be a
good idea to make sure that people don't use the escaping applied here
too wildly as anything other than the last label of a bus path.
|
| |
|
|
| |
This mirrors set_consume and makes the common use a bit nicer.
|
| |
|
|
| |
or services) as machine with machined
|
| |
|
|
| |
where appropriate
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This way we can unify handling of credentials that are attached to
messages, or can be queried for bus name owners or connection peers.
This also adds the ability to extend incomplete credential information
with data from /proc,
Also, provide a convenience call that will automatically determine the
most appropriate credential object for an incoming message, by using the
the attached information if possible, the sending name information if
available and otherwise the peer's credentials.
|
| |
|
|
|
| |
Just in order to bring things inline with the method and property
callbacks.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Message handler callbacks can be simplified drastically if the
dispatcher automatically replies to method calls if errors are returned.
Thus: add an sd_bus_error argument to all message handlers. When we
dispatch a message handler and it returns negative or a set sd_bus_error
we send this as message error back to the client. This means errors
returned by handlers by default are given back to clients instead of
rippling all the way up to the event loop, which is desirable to make
things robust.
As a side-effect we can now easily turn the SELinux checks into normal
function calls, since the method call dispatcher will generate the right
error replies automatically now.
Also, make sure we always pass the error structure to all property and
method handlers as last argument to follow the usual style of passing
variables for return values as last argument.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
callers session, user, seat or machine object
This way clients can skip invoking GetSessionByPID() for their own PID
or a similar call to access these objects.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
reply
https://bugs.freedesktop.org/show_bug.cgi?id=67273
|
| | |
|
| | |
|
|
|
Embedded folks don't need the machine registration stuff, hence it's
nice to make this optional. Also, I'd expect that machinectl will grow
additional commands quickly, for example to join existing containers and
suchlike, hence it's better keeping that separate from loginctl.
|
