Difference between revisions of "System maintenance"

From ArchWiki
Jump to: navigation, search
(added link to Pacnew/pacsave and improved readability)
m (Packages: added templates)
Line 14: Line 14:
 
* Search for .pac* files and merge them with configuration files (see [[Pacnew and Pacsave Files]]).
 
* Search for .pac* files and merge them with configuration files (see [[Pacnew and Pacsave Files]]).
  
* Check for out of date or unmaintained aur packages on your system (sometimes these can cause problems when you update).
+
* Check for out-of-date or unmaintained [[Arch User Repository|AUR]] packages on your system. Sometimes these can cause problems when you update.
  
* Check the size of /var and clear pacman's cache once in a while. A usefull tool to assist in this process is [https://aur.archlinux.org/packages.php?ID=37572 Cacheclean].
+
* Check the size of {{ic|/var}} and clear pacman's cache once in a while. A useful tool to assist in this process is {{AUR|cacheclean}}.
  
 
==Hardware==
 
==Hardware==

Revision as of 23:28, 19 June 2012

Read the News

The Arch Linux News is posted here: [1] You can subscribe to the rss feed by adding: [2] to your favorite feed reading software. You can also get news by subscribing to the Arch Announce mailing list: [3].

Pay special attention to news items with "manual intervention required" in their header. You can avoid a lot of trouble and embarrassment by reading the instructions in these news announcements and following them.

Packages

  • When you update, check pacman output for instructions related to updated packages.
  • Use pacman -Qdt to find orphaned packages, and pacman -Qo <file> to find out which packages that own individual files.
  • Check for out-of-date or unmaintained AUR packages on your system. Sometimes these can cause problems when you update.
  • Check the size of /var and clear pacman's cache once in a while. A useful tool to assist in this process is cachecleanAUR.

Hardware

  • Check disk (use fstab options to check at boot)
  • Search logs for errors (list scripts, tools to make this easier/more automated)
  • Look into errors as soon as possible - do not leave them unattended to.

Bad Practices

  • Linking random libraries together to get a program to work.
  • Updating once a year.
  • Copy-pasting commands into the terminal without at least reading man pages to understand what you are doing to your system.