1 May
2023
1 May
'23
noon
On Sun, 30 Apr 2023 22:11:27 -0500
J Leslie Turriff via tde-users <users(a)trinitydesktop.org> wrote:
I'm getting this strange situation again with
DCOP:
| $ dcop --user leslie --list-sessions
| Active sessions for user /home/leslie :
| .DCOPserver_pinto__0
| .DCOPserver_pinto__1
For some reason DCOP says I have two DCOP sessions. .DCOPserver_pinto__0 does not
respond to queries, so apparently it's dead or a ghost. .DCOPserver_pinto__1 works
normally.
I notice also that the output from dcop --help does not include the --suicide option?
Is
this a clue to what's going on?
How do I get rid of the one that doesn't respond?
Why do you want to? The double session seems to be normal (I have it too), but
they appear to both be attached to the same process ( ps -ef | grep dcop returns
only one line). The --suicide option has to do with session termination in the
dcop server and won't show up in the help for the client. See
https://manpages.org/dcopserver .
Unless you have reason to think that the presence of the unresponsive session
has broken something, I would just leave this one alone. I don't think you're
going to get zombie sessions multiplying out of bounds or anything like that.
E. Liddell