Re: /tmp accidentally filled
On Wednesday 03 December 2008 10:02:38 Kevin Mark wrote:
> On Wed, Dec 03, 2008 at 08:46:32AM +0000, Lisi Reisz wrote:
> > Here's another simpleton question. :-(
> >
> > I managed to backup onto my / partition. I have rm-ed most of the
> > resulting garbage. But I am left with a 100% full /tmp and df tells me
> > that this is overflow. I therefore need to do some more deleting. But I
> > am ashamed to say that I have not explored /tmp as much as I ought to
> > have, so my knowledge about what is usually/meant to be there is scant.
> > :-(
> >
> > Which, if any, of the following files ought I to keep and which can I
> > safely delete?
> > <quote>
> > gconfd-lisi kde-lisi keyring-iiiSCk ksocket-lisi orbit-lisi
> > ssh-PwasxA2979
> > </quote>
> >
> > Thanks.
> > Lisi
>
> TMP is not usually a place I need to clean. It is used for 'scratch
> space' when programs need to work on something temporarily. /tmp is
> usually only a few MB in size. On reboot, most Gnu system clean out tmp.
Thanks for your help, Kevin.
As I said, I have never had to do anything to tmp before. But it has not
cleaned up at boot and the fact that it is 100% full is causing problems.
This is a direct result of the mess I created when I messed up my backup. I
have deleted the bulk of the stuff wrongly placed on my root partition - so
most things are working fine again - and am left with this 100% filled tmp.
From what you say, I can safely delete the lot? After all, if it should have
been cleaned up automatically, it can't hurt if I clean it up manually?
The partition is now only ~20% full, so I have loads of space. But since at
least these files shouldn't be in tmp, I would rather delete them than start
messing around with the filing system.
Lisi
Reply to: