Difference between revisions of "System maintenance"

From ArchWiki
Jump to: navigation, search
(added link to Pacnew/pacsave and improved readability)
Line 2: Line 2:
 
== Read the News ==
 
== Read the News ==
  
The Arch Linux News is posted here: [http://www.archlinux.org/news] You can subscribe to the rss feed by adding: [http://www.archlinux.org/feeds/news] to your favorite feed reading software. You can also get news by subscribing to the Arch Announce mailing list: [http://mailman.archlinux.org/mailman/listinfo/arch-announce]
+
The Arch Linux News is posted here: [http://www.archlinux.org/news] You can subscribe to the rss feed by adding: [http://www.archlinux.org/feeds/news] to your favorite feed reading software. You can also get news by subscribing to the Arch Announce mailing list: [http://mailman.archlinux.org/mailman/listinfo/arch-announce].
  
 
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.  
 
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.  
Line 8: Line 8:
 
==Packages==
 
==Packages==
  
When you update, check pacman output for instructions related to updated packages
+
* When you update, check pacman output for instructions related to updated packages.
  
pacman -Qo to see if something owns them
+
* Use {{ic|pacman -Qdt}} to find orphaned packages, and {{ic|pacman -Qo <file>}} to find out which packages that own individual files.
  
Search for .pac* files (how to use locate, and suggest tools like meld and vimdiff)
+
* 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 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 /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].
  
 
==Hardware==
 
==Hardware==
  
check disk (fstab options to check at boot)
+
* Check disk (use fstab options to check at boot)
  
search logs for errors (list scripts, tools to make this easier/more automated)
+
* Search logs for errors (list scripts, tools to make this easier/more automated)
look into errors when they come up, do not wait
+
 
 +
* Look into errors as soon as possible - do not leave them unattended to.
  
 
==Bad Practices==
 
==Bad Practices==
  
link random libraries together to get a program to work
+
* Linking random libraries together to get a program to work.
  
update once a year
+
* Updating once a year.
  
copy - pasting commands into the terminal without at least reading the man page to see what you are actually doing to your system
+
* Copy-pasting commands into the terminal without at least reading man pages to understand what you are doing to your system.

Revision as of 21:47, 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 usefull tool to assist in this process is Cacheclean.

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.