Age | Commit message (Collapse) | Author |
|
Fixes #2091
|
|
Fixes for the service TTY reset logic and other stuff
|
|
Let's make sure we read it in a way compatible with non-aligned memory.
Fixes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812928
|
|
When checking a unit's state, don't ignore errors too eagerly, but generate proper error messages. Also, don't
synthesize an "unknown" state on error, but let the operation file. If a unit file isn't loaded treat this as
"inactive" as that's effectively what it means.
|
|
As it turns out all callers of check_unit_generic() already mangle unit names, or get the unit names directly from PID
1 (and hence arein normalized form anyway), hence there's no point in mangling then...
|
|
Some minor simplifications. Shouldn't change codepaths.
|
|
transient service
Otherwise we might end resetting /dev/console all the time when a transient service starts or stops.
Fixes #2377
Fixes #2198
Fixes #2061
|
|
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.
|
|
man: fix reference to an external man page
|
|
Noticed in pull request #2067.
|
|
.gitignore: add test-ask-password-api
|
|
|
|
|
|
systemctl is-enabled is not limited to wants.d - it also checks for
requires.d and alias links.
|
|
|
|
utf8.[ch] et al: use char32_t and char16_t instead of int, int32_t, i…
|
|
rework C11 utf8.[ch] to use char32_t instead of uint32_t when referring
to unicode chars, to make things more expressive.
[
@zonque:
* rebased to current master
* use AC_CHECK_DECLS to detect availibility of char{16,32}_t
* make utf8_encoded_to_unichar() return int
]
|
|
A number of fixes
|
|
Fixes #1692
|
|
Let's make sure our poll() calls don't get interrupted where they shouldn't (SIGALRM, ...), but allow them to be
interrupted where they should (SIGINT, ...).
Fixes #1965
|
|
Fixes: #2438
|
|
When the user specifies "foo*" as unit name glob expression, we shouldn't turn this into "foo*.service". Hence: only
append a suffix if the specified string isn't a glob expression.
Fixes: #2397
|
|
See: #2397
|
|
If we have many entries to add to an strv we really should try to be smarter than constantly realloc()ing the strv
array. Instead, grow it exponentially.
|
|
THis is otherwise really hard to read...
|
|
|
|
loopback file
An unlimited quota makes a lot of sense, but we really should try to propagate this onto the loopback file size, since
an infinitely sized file makes no sense.
Fixes: #2314 #2253
|
|
networkd: Add support to configure VXLAN Port
|
|
Ask password unicode fix
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=1301984
|
|
|
|
[v1] core: resolve specifier in config_parse_exec()
|
|
resolve: fix compare function for EtcHostItem
|
|
From dd0bc0f1
|
|
nss-resolve: fix gethostbyaddr h_aliases
|
|
Fix the comparison to include the first alias, which will
otherwise be left as a bogus pointer.
|
|
journald: minor fixes
|
|
nineteenth dnssec patch
|
|
zsh-completion: Escape results for `journalctl --unit`
|
|
shutdown: complain if process excluded from killing spree runs of the same rootfs as PID1 (v3)
|
|
Whenever we include a log level or facility in a journal string field, make sure the compiler checks for us that that's
actually the right thing to do.
|
|
Fixes: #2304
|
|
Fixes #2324.
|
|
This gets rid of the private DNSSEC TODO and moves it in the main TODO dump site, as the DNSSEC implementation is
pretty complete now, and the remaining bits are low-priority.
|
|
Lets make sure we always take notice of network changes before answering client requests.
This way, calls like SetLinkDNS() become race-free as the specified interface index is guarantee to have been processed
if it exists before we make changes to it.
|
|
DNS response
If we encounter NXDOMAIN, but find at least one matching RR in a response, then patch it to become SUCCESS. This should
clean up handling of CNAME/DNAMEs, and makes sure broken servers and those conforming to RFC 6604 are treated the same
way. The new behaviour opposes the logic suggested in RFC 6604, but given that some servers don't implement it
correctly, and given that in some ways the CNAME/DNAME chains will be incomplete anyway, and given that DNSSEC
generally only allows us to prove the first element of a CNAME/DNAME chain, this should simplify things for us.
|
|
|