On Wed, 27 Jul 2011 14:46, Richard Guenther
On Wed, 27 Jul 2011, Marcus Meissner wrote:
On Wed, Jul 27, 2011 at 02:37:49PM +0200, Pavol Rusnak wrote:
On 07/27/2011 01:35 PM, Marcus Meissner wrote:
It is a bad idea I think, you can not easily know if its your dconf-service binary.
I think that's the idea behind the script - to kill ALL running instances of dconf-service for ALL users.
How do you know some other programs are not called dconf-service?
If such a thing is required in an online update, you would mark it as a "rebootneeded" patch.
Or if you kill it in a moment of ongoing communication which applications do not expect to abort and thus causes them to crash.
Indeed a bad idea.
That only shows one thing: dconf-service is not able to do a "graceful-restart", apache2 can do it, this means it is possible per se, but not in dconf-service as it is. Marking it as a "rebootneeded" like the kernel or (g|eg|m|n)libc is the best way at this time, not the best way at all (graceful-restart) but for now. Just killing ANY program that is not able to do a graceful-restart is disrupting for a user and needs a warning beforhand (e.g. rebootneeded). Just my 2ct on this, Yamaban. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org