[systemd-bugs] [Bug 88996] systemd is ended by oom killer if MemoryLimit is exhausted.
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Feb 11 03:35:30 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=88996
Lennart Poettering <lennart at poettering.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |NOTABUG
--- Comment #5 from Lennart Poettering <lennart at poettering.net> ---
(In reply to Alexander Haensch from comment #4)
> It can be, that just the user systemd instance was killed.
> systemdctl, etc was not working anymore with some message that the
> connection timed out.
Well, that might have different reasons. For example, it might just be that
dbus-daemon was killed, which might cause communication timeouts.
> That would mean that it is possible to start the instance again, if the
> issue is happening again?
Well, yeah, systemd --user (in form of the user at .service service) can be
restarted any time.
Note that dbus-daemon cannot be restarted currently without losing all its
connections.
Anyway, I don't think there's anything to fix here in systemd, hence closing.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150211/8a8ba238/attachment-0001.html>
More information about the systemd-bugs
mailing list