On 06/19/2018 05:21 PM, Christopher Cox wrote:
Not sure what happened, but on one of our CentOS 7 host we had like 64
socket connects owned by pid 1 (systemd) in CLOSE-WAIT state. And
systemctl -a shows a bunch of lines like:
[email protected]:6556-10.32.3.10:55106.service (correspo
Not sure what happened, but on one of our CentOS 7 host we had like 64
socket connects owned by pid 1 (systemd) in CLOSE-WAIT state. And
systemctl -a shows a bunch of lines like:
[email protected]:6556-10.32.3.10:55106.service (corresponding
to the 64 CLOSE-WAIT connections)
I tri
On Tue, 19 Jun 2018 at 12:32:19 +, [email protected] wrote:
> The system is on a quite old kernel (3.18.44)
...
> At this point, things go wrong when
> recvmsg() is called on bus->input_fd with flags MSG_DONTWAIT|MSG_NOSIGNAL|
> MSG_CMSG_CLOEXEC. This syscall returns -22 (Invalid argument) whic
Hi,
I'm trying to migrate a sys V-based system to systemd. At the moment, I'm using
systemd 232. The system is on a quite old kernel (3.18.44), but I have enabled
the kernel configs listed in the systemd README. Things are mostly working
except systemd-logind.service fails to start. When I check
Hi,
On 13-06-18 17:05, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jun 13, 2018 at 04:55:27PM +0200, Hans de Goede wrote:
Hi,
On 12-06-18 19:11, Lennart Poettering wrote:
On Di, 12.06.18 11:33, Hans de Goede ([email protected]) wrote:
AFAIK the service actually doing the updates is supposed
