17 Aug
2013
17 Aug
'13
5:41 p.m.
I believe that this is exactly what I pointed out
earlier:
http://trinity-devel.pearsoncomputing.net/?0::11083
Yes. I remember.
The culprit is the desktop lock process. When I reboot my systems
my shutdown scripts remove garbage and spurious files and cleans
/tmp. When I then first log into Trinity /tmp/tdesocket-global does
not yet exist. Invoking the desktop lock creates /tmp/tdesocket-
global.
I understand a process like TDM using /tmp/tdesocket-global, but
seems to me user-spawned processes such as desktop locking should
use $TDEHOME/socket-`uname -n`.
Bug report 1633 filed.
Darrell