Hi Christian,
Why dbus is always proposed to be restarted:
I assume pid#13323 (dbus-daemon) runs under your logged-in user. Since
it seems that dbus-daemon is not part of your session 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.
I see no way to fix this behavior for jessie. It should be easyly
fixable in needrestart 2.0 due to it's user session handling.
HTH,
Thomas
On 11/22/2014 10:55 AM, Cristian Ionescu-Idbohrn wrote:
On Fri, 21 Nov 2014, Cristian Ionescu-Idbohrn wrote:
On Fri, 21 Nov 2014, Thomas Liske wrote:
could you please show the output of `needrestart -v`? Did you try to
restart dbus via needrestart?
Sure. Attached, output from:
# yes N | needrestart -v >/tmp/needrestart-v 2>&1
which ends with:
Running kernel seems to be up-to-date.
No services required to be restarted.
Though, if I run:
# needrestart -v
it ends with:
Running kernel seems to be up-to-date.
Services to be restarted:
Restart dbus? [yNas]
Please ignore the previous attachment.
A more recent output (after this morning upgrade), attached. This
time, both:
# yes N | needrestart -v >/tmp/needrestart-v 2>&1
and:
# needrestart -v
seem to produce identical output. Last lines:
Running kernel seems to be up-to-date.
Services to be restarted:
Restart dbus? [yNas]
Cheers,
--
:: WWW: http://fiasko-nw.net/~thomas/ ::
::: Jabber: xmpp:tho...@jabber.fiasko-nw.net :::
:: flickr: http://www.flickr.com/photos/laugufe/ ::
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
