2 May
2023
2 May
'23
6:02 p.m.
On 2023-05-02 09:18:14 Michael via tde-users wrote:
On Monday 01 May 2023 09:45:16 pm J Leslie Turriff via
tde-users wrote:
But there doesn't seem to be a zombie process associated with DCOP (or anything else,
really):
| ~
| ● ps aux | awk '$8 ~ /^[Zz]/'
| @12:52:29,root@pinto rc=0
| ~
| ● dcop --user leslie --list-sessions
| Active sessions for user /home/leslie :
| .DCOPserver_pinto__0
| .DCOPserver_pinto__1
|
| @12:52:45,root@pinto rc=0
so I'm wondering if the listed sessions are not produced just because of these files
(which I
suspect, based on the datestamp, are preserved across login/out sessions):
| ~
| $ la|grep DCOP
| lrwxrwxrwx 1 leslie users 33 2023-03-27
10:37:56 .DCOPserver_pinto_:0 -> /home/leslie/.DCOPserver_pinto__0
| -rw-r--r-- 1 leslie users 52 2023-03-27 10:37:56 .DCOPserver_pinto__0
| lrwxrwxrwx 1 leslie users 33 2023-04-29
15:53:26 .DCOPserver_pinto_:1 -> /home/leslie/.DCOPserver_pinto__1
| -rw-r--r-- 1 leslie users 54 2023-04-29 15:53:26 .DCOPserver_pinto__1
| @12:53:59,leslie@pinto rc=0
If I log out of my TDE session, then shell to /home/leslie and remove these files, maybe
that will clean up the issue? When I log back in via TDE, DCOP should recreate one of
them (presumably .DCOPserver_pinto__0)?
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
On 2023-05-01 20:25:55 E. Liddell via tde-users
wrote:
It's been since forever since I did anything with DCOP. If I read right up
thread you're doing this a root? So is there anyway to get the PID(s),
check which are zombies, then just kill them? Here's some commands to
start with (which you probably already know ;)
ps aux | grep -i dcop
ps aux | awk '$8 ~ /^[Zz]/'
^ last command blatently stolen from
https://itsfoss.com/kill-zombie-process-linux/
Best,
Michael
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt
op.org On Mon, 1 May 2023 17:30:24 -0500
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.