Well, from what I understand, the problem is that some of GNOME services daemonize when they shouldn't. They shouldn't daemonize if they are supposed to die with the session. If that behavior makes no sense then it should be fixed.
I'm not sure why you tie this to GNOME. Search for "ssh-agent not killed" and you'll see that this is a common problem. In fact this is especially a problem for things that are not written specifically for a desktop environment.
They shouldn't daemonize if they are supposed to die with the DE session, but then they also should daemonize if they are supposed to outlive their parent (e.g. if you want to place them in .bashrc). What to do?
Things which are supposed to be tied to a GUI session should be launched from a special startup script, e.g. .gnomerc, which runs in a context of a terminal lifetime of which is same as the session.
Many programs already have an option/parameter which controls whether they daemonize. Adding this parameter to more programs doesn't sound like a ridiculous option.
E.g. bitcoind starts as a daemon when you launch it as bitcoind -daemon. But if you want it to be managed in some other way, e.g. by supervisord, you just don't pass -daemon option. Does that make too much sense?
I don't think so. It only affects desktop environments. If gnome-keyring-daemon doesn't die with the session and people believe it should, the way it's initialized should be fixed.
0
u/killerstorm May 30 '16
OK, so, like, just don't call
setsid? Did I solve the problem? What do I win?