By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1633 - User desktop lock process creates /tmp/tdesocket-global
Summary: User desktop lock process creates /tmp/tdesocket-global
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2968
  Show dependency tree / graph
 
Reported: 2013-08-17 12:41 CDT by Darrell
Modified: 2018-08-30 02:52 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2013-08-17 12:41:18 CDT 
I understand a process like TDM creating /tmp/tdesocket-global, but user-spawned processes such as desktop locking should use $TDEHOME/socket-`uname -n`.

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. The culprit is the desktop lock process.

There are unexpected permissions problems, as noted in the dev mail list:

http://trinity-devel.pearsoncomputing.net/?0::11083

Resolution: ensure user-spawned processes do not create /tmp/tdesocket-global.