So, how do you determine which files your housekeeping script can sweep away without any issue? Some services write lock files to /tmp, some applications use it, and users use it. Most seasoned system administrators will tell you that you shouldn't remove files from /tmp unless you know that they're not being used, though. It's an unfortunate but necessary service to provide for your users. You can create housekeeping scripts and place them in crontab to periodically remove user files from the /tmp directory. So, what's a frustrated system administrator to do when you have dozens, hundreds, or even thousands of /tmp directories and users to deal with? The answer is to deploy user file housekeeping scripts. It's impossible to force users to comply with the policy of removing files from the /tmp directory in a timely manner. Plus, there are system housekeeping scripts in place for RHEL 7 and later. Note: An exception to not deleting user temp files after a reboot is to enable tmp.mount, but that's a topic for a different article. And rebooting doesn't get rid of user files, only system ones-even that relief is temporary until services restart and users open applications. What's not so cool is that your users like to use /tmp as their personal dumping ground without regard for the overall system's health, or your uptime bragging rights. Long uptimes are impressive, aren't they? It makes you one of the cool kids to brag about your 853-day uptime on a production system. Linux system administration skills assessmentīy a show of hands, how many of you like to reboot your servers? I don't see any hands.A guide to installing applications on Linux. Download RHEL 9 for free through the Red Hat Developer program.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |