![\"](\"https:\/\/www.heartinternet.uk\/blog\/wp-content\/uploads\/sshtricks-3.jpg\")
<\/p>\nSystem clean-up is something that should be performed on a regular basis. Depending on the number of users, the amount of use, and disk space limitations, you might need to do it every week, or you might be able to put it off for a few months. But it is important to clean up your server – a full file system can cause critical services to stop or disallow logins.<\/p>\n
There are four things to look at that can give you a clean running server easily.<\/p>\n
<\/p>\n
Applications that are currently being used might have temporary files open, and will crash or cause an error if the files are unexpectedly removed. Or anyone using the application might lose all their work since the last saved point.<\/p>\n If you reboot the server, it removes all temporary files, but you need a good reason to reboot your server, and cleaning Since To safely remove files from The first rule is: Never remove anything from Users get upset when administrators perform sweeping removals – no matter how necessary they are. A full The most effective method for cleaning The script is:<\/p>\n A great way to do this is to:<\/p>\n This way, if a user suddenly realises they need a file, you still have a copy, but you also have a clean It might be that you need to make changes to this routine – for example, if you can’t delete the files yourself, you can encourage your users to do so. Or you might need to exclude specific subdirectories in The same rules apply to There are system cleanup applications, such as tmpreaper and bleachbit, which can help you maintain a clean system.<\/p>\n Package managers are great – you don’t have to spend hours resolving dependencies for software. But they also tend to clutter the file system with old packages, dependencies, and cached files.<\/p>\n For Debian-based systems, run the following commands:<\/p>\n For Red Hat-based systems:<\/p>\n You can also install the yum-utils package and then issue:<\/p>\n <\/p>\n What are some of your housekeeping tricks for your server?<\/p>\n","protected":false},"excerpt":{"rendered":" System clean-up is something that you should do regularly. Here are four easy ways to keep your Linux server running smooth.<\/p>\n","protected":false},"author":2,"featured_media":16741,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,23],"tags":[],"class_list":{"0":"post-16739","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-dedicated-servers","8":"category-vps"},"yoast_head":"\n\/tmp<\/code> is writable by every user on the system, which can make it vulnerable. Many software programs write temporary files to the \/tmp<\/code> directory, and it can be difficult to determine which files to keep and which to remove.<\/p>\n\/tmp<\/code> is rarely enough of a reason for a full reboot.<\/p>\n\/tmp<\/code> can be written to by anyone, you might think that everyone’s files are vulnerable to removal. But the t<\/code> at the end of the permissions of \/tmp<\/code> (drwxrwxrwxt<\/code>) means that only original file owners can remove files. The root user can remove any file, but other users can’t touch them.<\/p>\n\/tmp<\/code>, you can use a script that looks for files that haven’t been modified for seven days and aren’t currently open. An example of this is:<\/p>\nfind \/tmp -mtime +7 | egrep -v \"`lsof -n +D \/tmp | awk 'NR>1 {print $9}'| tr \\\\n \\|`\"<\/code><\/p>\n![\"](\"https:\/\/www.heartinternet.uk\/blog\/wp-content\/uploads\/sshtricks-1.jpg\")
<\/p>\n\/home<\/h3>\n
\/home<\/code> without a verified backup.<\/p>\n\/home<\/code> won’t stop critical system operations, but it will annoy your users, who will, in turn, annoy you.<\/p>\n\/home<\/code> is to notify your users and get them to remove the files. You can run a script that lists all the files users haven’t accessed in over 180 days – if they haven’t used it in six months, it’s a good candidate for archiving or removing.<\/p>\nfind \/Users -atime +180 -type f<\/code><\/p>\n\n
\/home<\/code><\/li>\n\/home<\/code>.<\/p>\n\/home<\/code> so that users can retain important documents for later reference. You can also look into setting up file system quotas to ensure that your users take the responsibility for good housekeeping.<\/p>\n![\"](\"https:\/\/www.heartinternet.uk\/blog\/wp-content\/uploads\/sshtricks-2.jpg\")
<\/p>\n\/var<\/h3>\n
\/var<\/code> as they do to \/tmp<\/code>. Many applications write to a subdirectory of \/var<\/code>, but proceed with caution. Some web servers hold permanent files in \/var<\/code> under \/var\/www\/html<\/code> – so don’t wipe out an entire web service with an overzealous rm<\/code>.<\/p>\n![\"](\"https:\/\/www.heartinternet.uk\/blog\/wp-content\/uploads\/sshtricks-4.jpg\")
<\/p>\nCleaning up packages<\/h3>\n
$ sudo apt-get autoclean
\n$ sudo apt-get clean
\n$ sudo apt-get autoremove<\/code><\/p>\n$ sudo yum autoremove<\/code><\/p>\n$ package-cleanup -leaves -all<\/code><\/p>\n