<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I will try this. It is a bit complicated because the system in
question is also running ZFS and there are some bugs with that boot,
but I think I have worked them out enough. It may take me a few
days to find the time, however.<br>
<br>
On 11/03/2014 08:43 PM, Michael Biebl wrote:<br>
<span style="white-space: pre;">> Am 18.10.2014 um 21:49 schrieb
John Goerzen:<br>
>> Package: systemd<br>
>> Version: 215-5+b1<br>
>> Severity: grave<br>
>> Justification: renders package unusable<br>
>><br>
>> On investigating why my 8GB system, which was suddenly
running extremely<br>
>> slow and maxed out on swap, I discovered numerous
systemd-logind<br>
>> processes hogging RAM. Specifically, 41 processes using
4278148KB (or<br>
>> roughly 4GB) of RAM.<br>
>><br>
>> Here is some output from top:<br>
>><br>
><br>
> As John told me on IRC: He is running systemd-logind under
systemd-shim<br>
> on this particular system.<br>
> On other systems, where systemd is PID 1 he does not
experience this issue.<br>
> I told him to find out the current running systemd-logind
process which<br>
> owns the org.freedesktop.login1 D-Bus name via<br>
> "dbus-send --system --dest=org.freedesktop.DBus --print-reply<br>
> /org/freedesktop/DBus
org.freedesktop.DBus.GetConnectionUnixProcessID<br>
> string:org.freedesktop.login1"<br>
><br>
> and monitor that process via strace while periodically
checking with the<br>
> above command, when logind drops off the bus. So we can
eventually see<br>
> from the strace what happens at that time.<br>
><br>
> Unfortunately, when stracing the process, John is no longer
able to<br>
> reproduce the issue, as he told on IRC.<br>
><br>
> John, to narrow down the problem, could you please boot with<br>
> init=/bin/systemd to verify if this issue is indeed related
to systemd-shim.<br>
></span><br>
<br>
<br>
</body>
</html>