Home
last modified time | relevance | path

Searched refs:via (Results 1 – 25 of 49) sorted by relevance

12

/systemd-251/src/shared/
Dlocal-addresses.c185 const RouteVia *via) { in add_local_gateway() argument
189 assert(via); in add_local_gateway()
191 if (af != AF_UNSPEC && af != via->family) in add_local_gateway()
200 .family = via->family, in add_local_gateway()
201 .address = via->address, in add_local_gateway()
256 RouteVia via; in local_gateways() local
310 via.family = family; in local_gateways()
311 via.address = gateway; in local_gateways()
312 r = add_local_gateway(&list, &n_list, af, ifi, metric, &via); in local_gateways()
322 r = sd_netlink_message_read(m, RTA_VIA, sizeof(via), &via); in local_gateways()
[all …]
/systemd-251/docs/
DCREDENTIALS.md18 Traditionally, data of this nature has often been provided to services via
40 strings in unit files, acquired from another service dynamically via an
51 allow it, via `ramfs`.)
55 environment and the EFI System Partition (via `systemd-stub`). Such system
76 via D-Bus), this should only be used for credentials that aren't sensitive,
146 passing credentials via a path supplied over the command line use
148 credentials directory. For daemons that allow passing credentials via a path
175 via `systemd-creds cat`.
242 via `systemd` credentials. In particular, it might make sense to boot a
262 3. Credentials can also be passed into a system via the kernel command line,
[all …]
DJOURNAL_NATIVE_PROTOCOL.md10 `systemd-journald.service` accepts log data via various protocols:
12 * Classic RFC3164 BSD syslog via the `/dev/log` socket
13 * STDOUT/STDERR of programs via `StandardOutput=journal` + `StandardError=journal` in service files…
14 * Kernel log messages via the `/dev/kmsg` device node
15 * Audit records via the kernel's audit subsystem
16 * Structured log messages via `journald`'s native protocol
50 via the `memfd` logic.
64 key/value pair is serialized via one of two methods:
154 It might be wise to automatically upgrade to logging via the Journal's native
162 Journal logging in case they are invoked via systemd's service logic, where
[all …]
DUSER_GROUP_API.md2 title: User/Group Record Lookup API via Varlink
8 # User/Group Record Lookup API via Varlink
122 via `DynamicUser=` in unit files.
140 provided. When using the Varlink API, lookups into databases provided only via
141 NSS (and not natively via Varlink) are handled by the
144 synthesize NSS records for users/groups natively defined via a Varlink
149 between offering them via an NSS module or via a this Varlink API, either way
150 all records are accessible via both APIs, due to the bidirectional
151 forwarding. It is also possible to provide the same records via both APIs
DUSERDB_AND_DESKTOPS.md27 * [User/Group Record Lookup API via Varlink](USER_GROUP_API.md)
50 only revert back to the session after re-authentication via this system lock
65 via the `suspend=` argument to the
70 suspending, as communicated via this parameter.
80 `systemd-homed` exposes APIs to add, remove and make changes to local users via
82 hook-up. On the command line this is exposed via the
142 records via `accounts-daemon`, so that clients of the latter can consume them
DPASSWORD_AGENTS.md10 … different agents may watch via `inotify()`, and query the user as necessary. The answer is then s…
29 * The socket to send the response to is configured via `Socket=` in the `[Ask]` section. It is a `A…
39 … tool on the command line. Pass `--no-tty` to ensure the password is asked via the agent system. N…
DJOURNAL_FILE_FORMAT.md41 get via `journalctl -o export` or via `systemd-journal-gatewayd`. The export
78 * The format is designed to be read and written via memory mapping using multiple mapped windows.
97 trying to read it via a memory map.
251 with **n_data** needs to be explicitly checked for via a size check, since they
323 via `fdatasync()` should be enforced is after and before changing the **state**
342 this to watch for files changes. Since file writes done via `mmap()` do not
596 key for the HMAC is calculated via the externally maintained FSPRG logic for
624 done via binary search in the entry arrays starting with the header's
DCONTAINER_INTERFACE.md26 read-only (the latter via e.g. a read-only bind mount on itself) in order
84 via systemd's transient unit API (in case you have one container manager
88 be done via `systemd-machined`'s `CreateMachine()` API. Make sure to use the
141 restricted access to services via the `LoadCredential=` and `SetCredential=`
148 to services via `LoadCredential=` (see ...). The container manager can
253 matter much as it is communicated via the `$NOTIFY_SOCKET` environment
264 should be newline terminated. Passing this information via this file has the
DCONVERTING_TO_HOMED.md11 via entries in `/etc/passwd`, `/etc/shadow`, `/etc/group` and
22 * [User/Group Record Lookup API via Varlink](USER_GROUP_API.md)
DHACKING.md94 # Install a recent version of mkosi (either via your distro's package manager if
201 vscode's clangd extension, this is done via setting the `clangd.path` option to the path of the
261 …ontainer/virtual machine spawned by mkosi where systemd is running. mkosi makes this possible via a
262 handy SSH option that makes the generated image accessible via SSH when booted. The easiest way to …
DARCHITECTURE.md127 build an image and run the test under it via `qemu` or `systemd-nspawn`.
129 Most of those tests should be able to run via `systemd-nspawn`, which is
DJOURNAL_EXPORT_FORMATS.md18 When exporting journal data for other uses or transferring it via the network/local IPC the _journa…
27 This format can be generated via `journalctl -o export`.
DPREDICTABLE_INTERFACE_NAMES.md18 … similar to what is already done natively in udev for various device nodes via `/dev/*/by-path/` s…
52 …osely the scheme used for aliasing block device nodes and other device nodes in `/dev` via symlinks
DBUILDING_IMAGES.md142 missing. This can typically be addressed via `systemd-tmpfiles` lines that
145 copied or symlinked from the `/usr/share/factory/etc/` tree via the `C` or `L`
256 fields may be accessed from unit files and similar via the `%M` and `%A`
DHOME_DIRECTORY.md55 implemented via extended attributes on the directory itself: for each password
60 counter mode, using a key derived from the password via PBKDF2-HMAC-SHA512,
/systemd-251/src/core/
Dorg.freedesktop.systemd1.conf191 … <!-- Managed via polkit or other criteria: org.freedesktop.systemd1.Manager interface -->
333 … <!-- Managed via polkit or other criteria: org.freedesktop.systemd1.Job interface -->
347 … <!-- Managed via polkit or other criteria: org.freedesktop.systemd1.Unit interface -->
397 … <!-- Managed via polkit or other criteria: org.freedesktop.systemd1.Service interface -->
411 … <!-- Managed via polkit or other criteria: org.freedesktop.systemd1.Scope interface -->
/systemd-251/
DTODO91 by. Inform user code about path to this companion dir via env var, so that
101 passed in a file to the booted kernel (via initrd cpio, as usual). Usecase:
106 Why do this via a separate PE section? That's because the PCR state depends
137 LoadCredential=root.ssh.authorized-keys via drop-in to
139 nspawn's --load-credential=, through qemu's fw_cfg, or via systemd-stub's
150 only via explicit choice in boot menu: i.e. add explicit boot menu item for
158 via TPM2. Specifically, for StateDirectory= (and related dirs) use fscrypt to
168 with a key that can only be unlocked via a pristine pre-built Fedora
182 similar to the ssh keygen service that installs any SSH host key supplied via
203 * systemd-fstab-generator: support addition mount specifications via kernel
[all …]
DNEWS20 * Jobs started via StartUnitWithFlags() will no longer return 'skipped'
71 (as exposed via the SystemCallFilter= setting in service unit files).
90 entries, via the new /etc/kernel/entry-token file or the new
150 working display. (Controllable via a loader.conf setting.)
155 ID as selected via --entry-token= described above. The old name of
193 UID range via another UID mount map at container invocation
208 libsystemd-core.so can be configured via the meson option
296 devices and the associated governor, via the new
333 in via the new kernel command line option `systemd.set_credential=`
339 this way can be turned off via the new
[all …]
/systemd-251/units/
Dkexec.target11 Description=Reboot via kexec
Dsystemd-kexec.service11 Description=Reboot via kexec
/systemd-251/hwdb.d/
D70-mouse.hwdb476 # Logitech Anywhere MX 2S (via Logitech Unifying Receiver)
480 # Logitech Anywhere MX 2S (via Bluetooth)
484 # Logitech MX Master (via Logitech Unifying Receiver)
494 # Logitech MX Master (via Bluetooth)
503 # Logitech MX Master 2S (via Logitech Unifying Receiver)
512 # Logitech MX Master 2S (via Bluetooth)
/systemd-251/mkosi.default.d/opensuse/
D10-mkosi.opensuse58 # brought in via meson->python3
/systemd-251/shell-completion/zsh/
D_resolvectl76 {-p+,--protocol=}'[Look via protocol]:protocol:_resolvectl_protocols' \
D_systemd11 '--no-tty[Ask question via agent even on TTY]' \
/systemd-251/test/
DREADME.testsuite157 - starting a job: this is done via a Github webhook, so check if the HTTP POST
166 For infrastructure help, reaching out to Canonical via the #ubuntu-devel channel

12