| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Previously, using --accept would enable inetd-style socket activation in addition to per-connection operation. This is
now split into two switches: --accept only switches between per-connection or single-instance operation. --inetd
switches between inetd-style or new-style fd passing.
This breaks the interface of the tool, but given that it is a debugging tool shipped in /usr/lib/systemd/ it's not
really a public interface.
This change allows testing new-style per-connection daemons.
|
| |
|
|\
| |
| | |
Fix for #2467
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
unit, not just services
This moves the StartLimitBurst=, StartLimitInterval=, StartLimitAction=, RebootArgument= from the [Service] section
into the [Unit] section of unit files, and thus support it in all unit types, not just in services.
This way we can enforce the start limit much earlier, in particular before testing the unit conditions, so that
repeated start-up failure due to failed conditions is also considered for the start limit logic.
For compatibility the four options may also be configured in the [Service] section still, but we only document them in
their new section [Unit].
This also renamed the socket unit failure code "service-failed-permanent" into "service-start-limit-hit" to express
more clearly what it is about, after all it's only triggered through the start limit being hit.
Finally, the code in busname_trigger_notify() and socket_trigger_notify() is altered to become more alike.
Fixes: #2467
|
|/
|
|
| |
This is similar how we already do it for logind or machined.
|
|\
| |
| | |
Build sys and man fixes
|
| |
| |
| |
| |
| | |
Just a clarification. At least systemd-openqa-generator from
openqa gets this wrong.
|
| |
| |
| |
| |
| | |
Saying it is the "default" is misleading, because it is almost
never used.
|
| |
| |
| |
| | |
All distribution-specific code was removed ages ago.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This makes sure we never run two control processes at the same time, we cannot keep track off.
This introduces a slight change of behaviour but cleans up the definition of ExecStop= and ExecStopPost=. The former is
now invoked only if the service managed to start-up correctly. The latter is called even if start-up failed half-way.
Thus, ExecStopPost= may be used as clean-up step for both successful and failed start-up attempts, but ExecStop='s
purpose is clearly defined as being responsible for shutting down the service and nothing else.
The precise behaviour of this was not documented yet. This commit adds the necessary docs.
Fixes: #1254
|
| |
| |
| |
| |
| |
| | |
This adds a new switch --as-pid2, which allows running commands as PID 2, while a stub init process is run as PID 1.
This is useful in order to run arbitrary commands in a container, as PID1's semantics are different from all other
processes regarding reaping of unknown children or signal handling.
|
| |
| |
| |
| | |
Fixes: #2192
|
|\ \
| | |
| | | |
journalctl: add match for the current boot when called with devpath (v2)
|
| | | |
|
|\ \ \
| |/ /
|/| | |
journalctl --fields logic
|
| | |
| | |
| | |
| | | |
Fixes #2176
|
| |/
| |
| |
| |
| |
| | |
This adds two new calls to get the list of all journal fields names currently in use.
This is the low-level support to implement the feature requested in #2176 in a more optimized way.
|
| | |
|
| | |
|
|/
|
|
|
|
|
| |
event source
This should simplify handling of time events in clients and is in-line with the USEC_INFINITY macro we already have.
This way setting a timeout to 0 indicates "elapse immediately", and a timeout of USEC_INFINITY "elapse never".
|
| |
|
|
|
|
|
|
|
| |
Also introduce sd_journal_has_runtime_files() and
sd_journal_has_persistent_files() to the public API. These functions
can be used to easily find out if the open journal files are runtime
and/or persistent.
|
|\
| |
| | |
Resolved 2
|
| | |
|
| | |
|
| |
| |
| |
| | |
Docbook renders the man page as "[OPTIONS]--type" without it.
|
|\ \
| | |
| | | |
man: document special considerations when mixing templated service un…
|
| | |
| | |
| | |
| | |
| | |
| | | |
DefaultDependencies=no
Fixes #2189.
|
| | |
| | |
| | |
| | | |
belong into
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| | |
But also keep the old name as (undocumented) compatibility around.
The reload-or-try-restart was documented to be a NOP if the unit is not running, since the previous commits this is
also implemented. The old name suggests that the "try" logic only applies to restarting. Fix this, by moving the "try-"
to the front, to indicate that the whole option is a NOP if the service isn't running.
|
|/
|
|
|
| |
We generally document only the supported verbs, but not the compatibility verbs we also support, in order to keep the
documentation minimal.
|
|
|
|
|
| |
Avoid "mountpoint mounted" (word repetition),
"queriable" (no match in m-w.com and dict.cc).
|
| |
|
| |
|
|
|
|
|
| |
"VM virtualization" <=> "virtual machine virtualization", and double
virtualization is just incorrect in this context.
|
|
|
|
| |
Noticed in pull request #2067.
|
|\ |
|
| |
| |
| |
| |
| | |
systemctl is-enabled is not limited to wants.d - it also checks for
requires.d and alias links.
|
| |
| |
| |
| | |
Fixes: #2438
|
| |
| |
| |
| | |
See: #2397
|
|\ \
| | |
| | | |
networkd: Add support to configure VXLAN Port
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This patch add support to configure port
PortRange:
VXLAN bases source UDP port based on flow to help the
receiver to be able to load balance based on outer header flow.
DestinatinPort:
Allow configuring the default destination port on a per-device basis.
|
| | |
| | |
| | |
| | | |
Fixes #2324.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This changes the UseDomains= setting of .network files to take an optional third value "route", in addition to the
boolean values. If set, the passed domain information is used for routing rules only, but not for the search path
logic.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, .network files only knew a vaguely defined "Domains=" concept, for which the documentation declared it was
the "DNS domain" for the network connection, without specifying what that means.
With this the Domains setting is reworked, so that there are now "routing" domains and "search" domains. The former are
to be used by resolved to route DNS request to specific network interfaces, the latter is to be used for searching
single-label hostnames with (in addition to being used for routing). Both settings are configured in the "Domains="
setting. Normal domain names listed in it are now considered search domains (for compatibility with existing setups),
while those prefixed with "~" are considered routing domains only. To route all lookups to a specific interface the
routing domain "." may be used, referring to the root domain. An alternative syntax for this is the "*", as was already
implemented before using the "wildcard" domain concept.
This commit adds proper parsers for this new logic, and exposes this via the sd-network API. This information is not
used by resolved yet, this will be added in a later commit.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We have 126 broken links to sd-bus.html, it's nice to fix that.
Current version is mostly a stub, with a long list of links to other
pages. I think that's fine, especially that sd-bus might evolve
quite a bit before it is made public.
Not all of linked pages are written. Still missing:
sd_bus_can_send
sd_bus_get_name_creds
sd_bus_get_owner_creds
sd_bus_message_can_send
sd_bus_message_get_creds
sd_bus_message_set_allow_interactive_authorization
sd_bus_send
sd_bus_set_address
sd_bus_set_description
sd_bus_start
sd_event_set_prepare
sd-device
systemd.busname
|
| | | |
|