![](https://seccdn.libravatar.org/avatar/3d65ce348306eb0e36a6ec890e3e1b2d.jpg?s=120&d=mm&r=g)
On Tuesday 22 November 2005 10:14, eddieleprince wrote:
On Tuesday 22 November 2005 09:40, Laurent Renard wrote:
Le mardi 22 novembre 2005 à 08:04 +0000, eddieleprince a écrit :
On Tuesday 22 November 2005 07:06, Laurent Renard wrote:
Hello everyone,
my suse box is crashed since this morning. The erreor messages are : cannot start dcopserver and it seems that KDE cannot write to /tmp dir the directory is ok
Could you help me ?
Have you run out of space on the partition that hosts the /tmp directory?
He told me something like it, yes.
You could try and find out if there is a particularly file that is extremely large and using up all the space and delete that. Change to the /tmp directory and try
du -ks | sort -n
You could also try searching /var (if it is on the same partition as /tmp) as the problem could be an extra large log file.
Hope that helps.
As well as that excellent idea, you might also want to use 'find' for a different view of the situation. If /tmp is on its own partition, try on that. Something like: find /tmp -size +5000k for example will find and list any file in /tmp bigger than 5 megabytes. The nice thing about find is that you can add other criteria, and execute commands on the file set. You could (though perhaps you shouldn't in this case until you've at least looked to see what kind of files they are) do something like find /tmp -size +5000k -exec mv {} ~/bigfiles/ \; which would grab those large files and move them to 'bigfiles' if you wanted to use that directory as a holding area. There's the caveat that if you wanted to put them back exactly where you found them it might be fiddly, in that find will have recursed through the /tmp directory hierarchy. But if you want to, you can use -maxdepth to control how many levels of subdirectory find will drill down into. Man find has the details. HTH Fergus