Roger Qiu wrote on 19/08/14 01:42:
Hello Lennart,
I'm not familiar with the SystemD codebase
FYI, it's systemd not SystemD or systemD. Hardly a big deal, but
figured I'd correct while nitpicking other bits.
https://github.com/systemd/systemd so I don't where I could patch the
error
On Tue, 19.08.14 10:42, Roger Qiu (roger@polycademy.com) wrote:
Heya,
I'm not familiar with the SystemD codebase
https://github.com/systemd/systemd so I don't where I could patch
the error message.
On the other hand, is the kdbus production ready even though it
hasn't been merged into
Hello Lennart,
I'm not familiar with the SystemD codebase
https://github.com/systemd/systemd so I don't where I could patch the
error message.
On the other hand, is the kdbus production ready even though it hasn't
been merged into the kernel?
I'm curious what would be the procedure to
Hello Lennart,
The reason why you don't want explicit ordering is because of a slower
boot time?
When you are referring to patching them out, would that be from upstream
systemd/logind?
Thanks,
Roger
On 15/08/2014 7:41 PM, Lennart Poettering wrote:
On Fri, 15.08.14 15:04, Roger Qiu
On Fri, 15.08.14 15:04, Roger Qiu (roger@polycademy.com) wrote:
Hello Lennart,
Thanks for answering.
Is there any way to enforce ordering to make this error not occur?
You could order systemd-logind.service After= dbus.service. That way
dbus is started first, and logind second. And
On Thu, 17.07.14 11:49, Roger Qiu (roger@polycademy.com) wrote:
Hi,
(sorry for the late response)
Are you saying that logind should be terminated first then dbus
should be terminated second?
Yes, dbus should best be stopped after logind.
In what situations would their termination
Hello Lennart,
Thanks for answering.
Is there any way to enforce ordering to make this error not occur?
Or what's the best way to hide that warning?
Or when is the ETA for kdbus?
Thanks,
Roger
On 15/08/2014 8:38 AM, Lennart Poettering wrote:
On Thu, 17.07.14 11:49, Roger Qiu
On Wed, 16.07.14 14:53, Roger Qiu (roger@polycademy.com) wrote:
Hello everybody,
I always receive this error:
```
|Jul 14 08:27:57 matrix-node systemd-logind[1339]: Failed to abandon session
scope: Connection reset by peer|
```
When I shutdown a NixOS instance.
Googling
Hello everybody,
I always receive this error:
```
|Jul 14 08:27:57 matrix-node systemd-logind[1339]: Failed to abandon session
scope: Connection reset by peer|
```
When I shutdown a NixOS instance.
Googling around didn't bring up any useful results. What does this error
mean, and why does
