On Fr, 02.03.18 10:22, Hongzhi, Song (hongzhi.s...@windriver.com) wrote:
> On 2018年03月01日 17:50, Lennart Poettering wrote:
> > On Do, 01.03.18 14:44, Hongzhi, Song (hongzhi.s...@windriver.com) wrote:
> >
> > > Thank you very much. It dose work.
> > >
> > > Would you tell me that how the
On Do, 01.03.18 16:13, Thomas Blume (thomas.bl...@suse.com) wrote:
> On Thu, 1 Mar 2018, Lennart Poettering wrote:
>
> > > The kernel must not set policy on what is a source of wake ups. Setting
> > > this up so that we do not get a regression in functionality compared
> > > to old style S3
When dbus-daemon carries out a mixture of systemd and traditional
(non-systemd) activation, we get a process tree like this:
systemd --user (init.scope)
|- dbus-daemon --session (dbus.service)
| |- (babysitter process)
|
On Fr, 02.03.18 15:16, Simon McVittie (s...@collabora.com) wrote:
> When dbus-daemon carries out a mixture of systemd and traditional
> (non-systemd) activation, we get a process tree like this:
>
> systemd --user (init.scope)
> |- dbus-daemon --session