Some *nix systems clean /tmp on every reboot and I have been considering
making that part of our startup. Our /tmp does not fill up much even after
a month so it is not that big a deal. I was thinking of making /tmp a
separate virtual file system like swap.
I agree with Mark on /var. You may want to consider it on a file by file
basis.
tom
- - - - - - - - - - - -
Toto, I have a feeling we're not in the mainframe world any more.
_/) Tom Shilson
~~~~~ GEDW & VM System Services
Aloha Tel: 651-733-7591 tshilson at mmm dot com
Fax: 651-736-7689
Linux on 390 Port <[EMAIL PROTECTED]> wrote on 12/12/2004 04:54:15
PM:
> There's way too much stuff under /var to do something like that. If
> you've got logrotate running, most of it will take care of itself.
> You might want to purge "old" stuff out of /var/tmp/, but I would
> look very carefully at anything else, first.
>
> For your empty directory example, you're not checking dates, so they
> may have just been created when your scan runs. While the contents
> of /tmp aren't guaranteed, I don't think that kind of behavior is
expected.
>
> Mark Post
<...snip...>
> I was planning to perform some housekeeping cleanup on a regular basis
for
> /tmp by including the following command in a cron:
>
> find /tmp -atime +30 -type f -print0 | xargs -0 rm
>
> I was going to do the same for the /var directory and got to thinking
that
> maybe I will get more than I bargain for. What is everyoneâs opinion
about
> removing all files that have not been accessed in 30 days for directory
> /var? Am I being over zealous?
>
> What about directories? Should I remove empty directories within /tmp and
> /var using a command like?:
>
> find /tmp âempty -type d -print0 | xargs -0 rmdir
>
> I welcome all comments. Thanks.
>
> Peter
<...snip...>
