From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; Linux 2.4.7-10smp i686)

Description of problem:
We have been having some problems with KDE and the way that temporary files are
built on the server.  Certain files are never deleted and in time cause KDE to
experience failures.  We have close to 900 unique users on 400 thin clients. 
People are logging in and out of the system all day, and move around between
locations.  We also have some users that have 2 thin clients on their desk and
log into both of them at the same time.

I have found the following areas that seem to need attention.

* The system builds a file called .DCOPserver_<server_name>_<device_name> and
then does a soft link to .DCOPserver_<server_name>  in their home directory. 
When they log in for the second time on another thin client, the soft link is
then moved to the new device even though both sessions are still in use and
active.

* .fam<unique_number> files are built in /tmp and look like this:
srw-------    1 ksnyder  nobody          0 Jan 10 10:39 .fam00fUmD
Permissions therefore for the first person to write the file.  If the server is
up long enough, won't those <unique_numbers> eventually come up again and cause
problems?

* In /tmp it is building files that look like this-->
-rw-------    1 lhilton  lhilton       211 Jan  8 08:09 dcop0tEQrX
If that unique number comes up again, the next person won't be able to overwrite
the file and that will cause problems.

* In the /tmp/.ICE-unix directory, it is building special files that look like
this-->
srwx------    1 gmatting gmatting        0 Jan 10 07:17 1179
It looks to me like they are the process number of the application that needs
the pipe.  Over time, the process numbers flip over again and people were
getting those ICE errors because they didn't have access rights to overwrite the
older file from the previous user.

This is what we get with the ICE problem:
_IceTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_IceTransMakeAllCOTSServerListeners: server already running
KSMServer: Error listening for connections: Cannot establish any listening socke
ts
KSMServer: Aborting

It seems to me that all of these examples should be renamed to better handle
different users and devices.  For instance the ICE files could be called
1179_mjohnson_xtubegg:0  , they would never collide then with other users and
also not with himself on another device that is active at the same time.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Use KDE with many users at the same time.
2.
3.
	

Actual Results:  Tempory files began to grow, never are deleted.

Expected Results:  Temp files should either delete, or better yet be named in a
way that collision never happens.

Additional info: