Skip to main content

/tmp 94%


1 comment

  • MilesWeb

    Managing the /tmp directory on a server requires caution, as it is a temporary storage location that various processes and applications use. Before deleting anything, it's important to understand what files are present and if they can be safely removed.

    Here are some steps to help you safely manage the /tmp directory:

    Identify Large Files:
    Use the following command to list the largest files in the /tmp directory:

    sudo du -h /tmp | sort -rh | head -n 10

    This will show you the largest files and directories in /tmp. Review the list to identify any unnecessary or old files that can be deleted.

    Check for Important Processes:
    Before deleting files, check if there are any active processes or services that are currently using /tmp. You can use the lsof command to list open files and processes:

    sudo lsof +D /tmp

    Review the output to ensure that no critical processes are actively using files in /tmp. If there are, it's best to leave those files untouched.

    Remove Old Files:
    Delete files that are old or unnecessary. You can use the find command to locate and remove files older than a certain number of days. For example, to remove files older than 7 days:

    sudo find /tmp -type f -mtime +7 -exec rm {} \;

    This command will remove all regular files (not directories) in /tmp that are older than 7 days.

    Clear Specific Subdirectories:
    Sometimes, certain subdirectories within /tmp are known to accumulate unnecessary files. For example, session files for web applications might be stored in a subdirectory. Identify such subdirectories and clean them selectively.

    Reboot the Server:
    If possible, consider rebooting the server after cleaning the /tmp directory. This ensures that any lingering processes releasing files will release them upon restart.

    Always exercise caution when deleting files, especially in critical system directories. If you're unsure about a particular file or directory, it's best to investigate further or seek advice from your hosting provider or system administrator before taking any action.


Please sign in to leave a comment.