On Sunday 07 January 2007 11:33, Steve Searle wrote:
Around 11:20am on Sunday, January 07, 2007 (UK time), Anne Wilson
scrawled:
> On Sunday 07 January 2007 11:03, Ed Greshko wrote:
> > Anne Wilson wrote:
> > > /tmp is filling up rapidly. I'm guessing that it would be safe
> > > enough to delete everything dated previous to the last bootup. Am I
> > > right?
> >
> > The most logical question is, what is /tmp filling up with? I can't
> > say that in a normally operating system I've seen /tmp filling up
> > "rapidly" without a cause and I'm not the one to go willy-nilly
> > deleting things without known why they are being created.
>
> Duh! I mis-read the logfile line. It's not really filling up, though
> there are things that I think should be deleted.
Anne,
I run the following command in a cron job:
tmpwatch --mtime --verbose --verbose 168 /tmp
You may not want the --verbose, and check the manpage for the --mtime
option, but basically this deletes all files in /tmp that have not been
modified for 168 hours or more.
I have a problem, Steve. Running that command from a root konsole works fine,
so I set it to run as a cron job every Wednesday. Now I find that from both
boxes where I set this up I'm getting root emails that say
/bin/sh: tmpwatch: command not found
What could be wonrg?
Anne