2 May
2023
2 May
'23
2:45 a.m.
On 2023-05-01 20:25:55 E. Liddell via tde-users wrote:
On Mon, 1 May 2023 17:30:24 -0500
J Leslie Turriff via tde-users <users(a)trinitydesktop.org> wrote:
Scripting's a bit of an unusual use case. Does passing --all-sessions
still result in a hang? Is there a pattern to which session is
unresponsive (always the first, or always the second), or is it random?
No, no.
--all-sessions always succeeds, but then there is no way to determine if one of
the sessions that it returns is dead or not, except by sending a message to each.
If I send a message to one that is dead the script will hang.
It would be nice if it returned a status code (or anything) instead of hanging.
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.
So, when scripting, how does one know which one to avoid? If one picks
the wrong one it hangs the session.
I suppose you could fork off two instances of a simple test and see which
one exits and which hangs (and then kill the hanging one), but that's more
of a kludge than a solution . . .
I agree.
E. Liddell
Leslie
--
Platform: GNU/Linux
Hardware: x86_64
Distribution: openSUSE Leap 15.4
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.13
tde-config: 1.0