On Sat, 22 Nov 2014, Thomas Liske wrote:
>
> Why dbus is always proposed to be restarted:
>
> I assume pid#13323 (dbus-daemon) runs under your logged-in user.
Yes. This is what I find in the process list:
...
me 13322 0.0 0.0 24484 1292 pts/11 S Nov08 0:00
/usr/bin/dbus-launch --autolaunch a379e709c99a28d4553793d3510d5297
--binary-syntax --close-stderr
me 13323 0.0 0.0 42244 1884 ? Ss Nov08 0:15
/usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
...
me 15133 0.0 0.0 337604 2904 ? Sl Nov09 0:00
/usr/lib/at-spi2-core/at-spi-bus-launcher
me 15137 0.0 0.0 42108 2476 ? S Nov09 0:01 \_
/usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork
--print-address 3
...
message+ 32351 0.0 0.0 42240 2596 ? Ss Nov21 0:00
/usr/bin/dbus-daemon --system
> Since it seems that dbus-daemon is not part of your session
The WM is wmaker and init is sysv.
> needrestart tries to find a runlevel script to restart it. While
> looking at the package content of dbus (after finding it by a dpkg
> -S /usr/bin/dbus-daemon call) needrestart finds dbus's rc script and
> suggests to restart it.
>
> Howto fix / workaround:
>
> Not that easy. needrestart 1.2 did not try to identify processes of user
> sessions to distinguish them from processes spawned by system services.
> You could add an ignore statement to needrestarts config - but this
> would hide any required restarts of the system bus.
Right. I don't want to do that.
> I see no way to fix this behavior for jessie.
No worries. This is unstable.
> It should be easyly fixable in needrestart 2.0 due to it's user
> session handling.
But that worries me a bit, given my setup (sysvinit and wmaker).
Still, I have to admit, I'm not a "session handling" connoisseur.
--
Cristian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
