| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
reset usec when bumping hours/minutes
|
|
|
|
| |
CID #1320855.
|
|
|
|
| |
Fixes: #1969
|
|
|
|
| |
this fixes 2655
|
|
|
|
|
|
|
|
| |
Running "udevadm test-builtin path_id /sys/devices/platform/" results
in a segmentation fault.
The problem is that udev_device_get_subsystem(dev) might return NULL
in a streq() call. Solve this problem by using streq_ptr() instead.
|
|
|
|
|
|
|
| |
Das ist verboten!
src/basic/strbuf.c:162:23: runtime error: null pointer passed as argument 2,
which is declared to never be null
|
|
|
|
|
|
| |
Fixes fall-out from 8b3aa503c171acdb9ec63484a8c50e2680d31e79.
Fixes: #2635
|
|
|
|
| |
Fixes: #2632
|
|
|
|
| |
Fixes: #2457
|
|
|
|
| |
Fixes: #2597
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ISO/IEC 9899:1999 §7.21.1/2 says:
Where an argument declared as size_t n specifies the length of the array
for a function, n can have the value zero on a call to that
function. Unless explicitly stated otherwise in the description of a
particular function in this subclause, pointer arguments on such a call
shall still have valid values, as described in 7.1.4.
In base64_append_width memcpy was called as memcpy(x, NULL, 0). GCC 4.9
started making use of this and assumes This worked fine under -O0, but
does something strange under -O3.
This patch fixes a bug in base64_append_width(), fixes a possible bug in
journal_file_append_entry_internal(), and makes use of the new function
to simplify the code in other places.
|
|
|
|
| |
from e903182e5b0daa941de47a9c08c824106cec7fe0
|
| |
|
|
|
|
| |
no change in behaviour
|
| |
|
|\
| |
| | |
units: don't try to mount the mqueue fs if we lack the privileges for it
|
| |
| |
| |
| | |
See https://github.com/systemd/systemd/pull/2576#discussion-diff-52592680
|
|\ \
| | |
| | | |
Random fixes
|
| | |
| | |
| | |
| | | |
Fixes: #1981
|
| | |
| | |
| | |
| | |
| | |
| | | |
See:
https://lists.freedesktop.org/archives/systemd-devel/2016-February/035740.html
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Don't ever permit successful user or group lookups if no UID/GID mapping is
actually applied. THis way, we can be sure that nss-mymachines cannot be used
to insert invalid cache entries into nscd's cache.
https://bugzilla.redhat.com/show_bug.cgi?id=1285339
|
| | | |
|
| | | |
|
| | | |
|
| |/
|/| |
|
|\ \
| | |
| | | |
tests: add test for https://github.com/systemd/systemd/issues/1981
|
| | |
| | |
| | |
| | | |
This is a follow-up to https://github.com/systemd/systemd/pull/2493
|
| |/ |
|
|\ \
| | |
| | | |
man: follow up fixes for #2575
|
| | | |
|
|\| |
| |/
|/| |
A variety of man page fixes
|
| |
| |
| |
| |
| |
| |
| |
| | |
The "is-enabled" command doesn't care whether the symlinks are declared in the
[Install] section of a unit file or not, when returning "enabled". Any alias,
.wants/ or .requires/ symlinks suffice.
Fixes: #975
|
| |
| |
| |
| | |
Fixes: #846
|
| |
| |
| |
| | |
Fixes: #1502
|
| |
| |
| |
| |
| |
| | |
(And similar for resolved)
Fixes: #1630
|
| |
| |
| |
| |
| | |
Fixes: #1774
Fixes: #1090
|
| |
| |
| |
| | |
References: #2468
|
|/
|
|
| |
Fixes: #2523
|
|\
| |
| | |
cgroup: remove support for NetClass= directive
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Support for net_cls.class_id through the NetClass= configuration directive
has been added in v227 in preparation for a per-unit packet filter mechanism.
However, it turns out the kernel people have decided to deprecate the net_cls
and net_prio controllers in v2. Tejun provides a comprehensive justification
for this in his commit, which has landed during the merge window for kernel
v4.5:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bd1060a1d671
As we're aiming for full support for the v2 cgroup hierarchy, we can no
longer support this feature. Userspace tool such as nftables are moving over
to setting rules that are specific to the full cgroup path of a task, which
obsoletes these controllers anyway.
This commit removes support for tweaking details in the net_cls controller,
but keeps the NetClass= directive around for legacy compatibility reasons.
|
|\ \
| | |
| | | |
tty-ask-password: Split out password sending
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a piece of refactoring I've done while looking for a solution to bug #2378.
It separates the password sending from `parse_password`, which only needs to know
about the socket path and the list of passwords to send.
As a caveat, the `ask_password_tty` path needs to construct a one-password strv, too.
|
|\ \ \
| |_|/
|/| | |
Coredump fixes and more
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Corrects an incompatibility introduced with 36c16a7cdd6c33d7980efc2cd6a2211941f302b4.
Fixes: #2537
|
| | |
| | |
| | |
| | | |
Let's make things more obvious by placing the parse_usec() invocation directly in config_parse_service_timeout().
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Let's add an extra-safety net and change UID/GID to the "systemd-coredump" user when processing coredumps from system
user. For coredumps of normal users we keep the current logic of processing the coredumps from the user id the coredump
was created under.
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=87354
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The kernel sets RLIMIT_CORE to 0 by default. Let's bump this to unlimited by
default (for systemd itself and all processes we fork off), so that the
coredump hooks have an effect if they honour it.
Bumping RLIMIT_CORE of course would have the effect that "core" files will end
up on the system at various places, if no coredump hook is used. To avoid this,
make sure PID1 sets the core pattern to the empty string by default, so that
this logic is disabled.
This change in defaults should be useful for all systems where coredump hooks
are used, as it allows useful usage of RLIMIT_CORE from these hooks again. OTOH
systems that expect that coredumps are placed under the name "core" in the
current directory will break with this change. Given how questionnable this
behaviour is, and given that no common distro makes use of this by default it
shouldn't be too much of a loss. Also, the old behaviour may be restored by
explicitly configuring a "core_pattern" of "core", and setting the default
system RLIMIT_CORE to 0 again via system.conf.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With this change processing/saving of coredumps takes the RLIMIT_CORE resource limit of the crashing process into
account, given the user control whether specific processes shall core dump or not, and how large to make the core dump.
Note that this effectively disables core-dumping for now, as RLIMIT_CORE defaults to 0 (i.e. is disabled) for all
system processes.
|