tmpwatch - removes files which haven’t been accessed for a period of time
tmpwatch [-u|-m|-c] [-MUadfqstvx] [--verbose] [--force] [--all]
[--nodirs] [--test] [--fuser] [--quiet]
[--atime|--mtime|--ctime] [--dirmtime] [--exclude
[--exclude-user <user>] <hours> <dirs>
tmpwatch recursively removes files which haven’t been accessed for a given number of hours. Normally, it’s used to clean up directories which are used for temporary holding space such as /tmp.
When changing directories, tmpwatch is very sensitive to possible race conditions and will exit with an error if one is detected. It does not follow symbolic links in the directories it’s cleaning (even if a symbolic link is given as its argument), will not switch filesystems, skips lost+found directories owned by the root user, and only removes empty directories and regular files.
By default, tmpwatch dates files by their atime (access time), not their mtime (modification time). If files aren’t being removed when ls -l implies they should be, use ls -u to examine their atime to see if that explains the problem.
If the --atime, --ctime or --mtime options are used in combination, the decision about deleting a file will be based on the maximum of these times. The --dirmtime option implies ignoring atime of directories, even if the --atime option is used.
The hours parameter defines the threshold for removing files. If the file has not been accessed for hours hours, the file is removed. Following this, one or more directories may be given for tmpwatch to clean up.
Make the decision about deleting a file based on the file’s atime (access time). This is the default.
Note that the periodic updatedb file system scans keep the atime of directories recent.
cron(1) , ls(1) , rm(1) , fuser(1)
GNU-style long options are not supported on HP-UX.
Erik Troan <email@example.com>
Preston Brown <firstname.lastname@example.org>
Nalin Dahyabhai <email@example.com>
Miloslav Trmac <firstname.lastname@example.org>
Table of Contents