Export translations

Settings

Group

Language

Format

Export for off-line translation

Export in native format

<languages/>
__TOC__

<div lang="en" dir="ltr" class="mw-content-ltr">
=Overview=
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This article contains tips and best practices for keeping your system in optimal condition.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=Home Cache=
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The hidden {{ic|.cache}} folder in your home directory is used by many parts of your system. This includes downloads, thumbnails, desktop resources, and more.<br />
While it is generally safe to remove everything in your {{ic|~/.cache}} folder, it may be more advisable to inspect its contents and selectively remove items instead.<br />
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To generate a sorted list of contents and sizes:
{{UserCmd|command=du -sh ~/.cache/* | sort -h}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To automatically purge all {{ic|.cache}} files that have not been accessed in 100 days:
{{UserCmd|command=find ~/.cache/ -type f -atime +100 -delete}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=Journal and Logs=
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Log files & the systemd journal do the same thing in different ways. They keep a record of everything that happens on your system.<br />
For more information and tips on automated maintenance please see the dedicated page [[Limit the size of .log files %26 the journal]]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Systemd Journal==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The journal keeps logs of system activity. This can be important for troubleshooting, but sometimes the log size can grow rather large.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To report the current size:
{{UserCmd|command=journalctl --disk-usage}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To remove all but the most recent entries by size or time:
{{UserCmd|command=journalctl --vacuum-size=50M}}
{{UserCmd|command=journalctl --vacuum-time=2weeks}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To set a maximum size for the journal you can uncomment and edit the following line in {{ic|/etc/systemd/journald.conf}}:
 SystemMaxUse=50M
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==System logs at /var/log/*==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
While most things use the newer systemd journal (journalctl), there is still some software that uses the older /var/log/ directory.<br />
For more information and some tips on maintaining it, please see the relevant section of [[Limit the size of .log files & the journal#Managing /var/log/* files|this page]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=Packages and Updates=
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Keeping your System Updated==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
On a rolling release distribution it is essential to keep your system fully updated.  Manjaro provides a few ways to keep your system updated.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You can use the GUI tool [[Pamac]] directly or via the update notifier
* You can use the GUI tool [[Octopi]] directly or via the update notifier
* You can use the [[Pamac#Updating_the_System|Pamac CLI]]
* You can use the [[Pacman_Overview#Installing_Updates|Pacman CLI]]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Avoiding Partial Updates==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{BoxDanger|danger|Partial updates are not supported under any circumstances}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It is of critical importance to ensure you don't end up in a state where your system is partially upgraded.<br />
It is not uncommon for systems in partially updated state to end up in a critical failure state.<br />
Here are some rules to help you avoid this undesired situation.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Don’t update the local package database (metadata) without also updating the system
* You may install a single package using {{ic|pacman -S <pkgname>}} but this may yield a 404 error if your metadata is not current
* Don't use {{ic|pacman -Sy}}, {{ic|pacman -Syy}}, {{ic|pacman -Syuw}} as this will update the metadata but not sync the packages to your system
* Always sync metadata and packages together {{ic|pacman -Syu}}
* Don't add packages to pacman's or pamac's ignore list
* If you just want to check to see what updates are available use the command {{ic|checkupdates}}.  This provides a safe way to check for upgrades to installed packages without pulling metadata at the same time
* When [[Switching_Branches|switching branches]] or [[Pacman-mirrors|switching mirrors]] always sync your systems metadata and packages using {{ic|pamac update}} or {{ic|pacman -Syu}}
* If you get 404 in connection with a branch switch you may force sync metadata by doubling the '''y''' argument {{ic|pacman -Syyu}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Removing Orphans==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As packages are added, built and removed it is not uncommon to have unneeded dependencies, also called orphans, building up over time.  While orphans are not harmful, they take up space on the disk and consume network bandwidth as they are continually updated.  Luckily, there are a couple of easy ways to view and remove orphans.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To use pamac follow [[Pamac#Dealing_with_Orphaned_Packages|this guide]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To use pacman follow [[Pacman_Overview#Viewing_and_Removing_Orphans|this guide]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Package Cache==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
By default both pamac and pacman keep a cache of downloaded packages on the system. This can be helpful if you need to copy or downgrade a package.<br />
But the cache can grow to include dozens of each package resulting in gigabytes of space.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To use pamac follow [[Pamac#Cleaning_the_Cache|this guide]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To use pacman follow [[Pacman_Overview#Cleaning_the_Cache|this guide]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Pacnew and Pacsave files==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
A .pacnew file may be created during a package upgrade to avoid overwriting a file which already exists. A .pacsave file may be created during a package removal, or by a package installation of a package that was removed. These files require manual intervention from the user and it is good practice to handle them regularly.  The program {{ic|pacdiff}} can help manage this process. For example, here is what it looks like when the {{ic|/etc/default/grub}} grub file has changed:
 DIFFPROG=meld pacdiff -s
 ==> pacnew file found for /etc/default/grub
 :: (V)iew, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/s/r/o/q]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* {{ic|V}} shows the differences between the two files
* {{ic|S}} skips to the next change and allows you to deal with it later or manually
* {{ic|R}} keeps your existing file and delete the new file
* {{ic|O}} overwrites the existing file with the new file
* {{ic|Q}} quits the process without making further changes
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Unfortunately, there is no perfect road map for how to deal with these files. If you keep the original config file, and the syntax has changed, the program may stop working or fail to use the existing config. If you remove the original file and use the new file without any changes, all your configuration settings can be overwritten.  Sometimes, you need to combine pieces from the new and old files to make everything to work.  In these situations it is better to integrate the files manually.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For more detailed information, please see review the Arch Wiki [[#See_Also|linked below]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=Time and Date=
[[File:Msm-time-date.png|thumb|left|350px]]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Keeping the system time accurate may seem unimportant but certain network related services may malfunction if the time is out of sync.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The easiest way to ensure the time is being properly synchronized is the GUI tool included in '''Manjaro Settings Manager''' which is pictured to the left. Simply check the box next to "Set time and date automatically".
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
An alternative is to use systemd via the systemd-timesyncd service. This can be easily enabled with one of these commands:
{{UserCmd|command=timedatectl set-ntp true}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=sudo systemctl enable --now systemd-timesyncd}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=See Also=
* The Arch Wiki guide on [https://wiki.archlinux.org/index.php/System_maintenance System Maintenance]
* The Arch Wiki guide on [https://wiki.archlinux.org/index.php/Pacman/Pacnew_and_Pacsave Pacnew and Pacsave] files
* The [[Pacman_Overview|Pacman wiki article]]
* The [[Pamac|Pamac wiki article]]
</div>
<br />

[[Category:Contents Page{{#translation:}}]]