Difference between revisions of "Profile-sync-daemon"

From ArchWiki
Jump to: navigation, search
Line 1: Line 1:
[[Category:Web Browser]]
[[Category:Web Browser]]
[[Category:Scripts (English)]]
[[Category:Daemons and system services]]
[[Category:Daemons and system services]]

Revision as of 18:22, 23 April 2012

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end

Benefits of Psd

Running this daemon is beneficial for two reasons:

  1. Reduced wear to physical discs
  2. Speed

Since the profile(s), browser cache, etc. are relocated into tmpfs, the corresponding onslaught of I/O associated with using the browser is also redirected from the physical disc to RAM, thus reducing wear to the physical disc and also greatly improving browser speed and responsiveness. The access time of RAM is on the order of nanoseconds while the access time of physical discs is on the order of milliseconds. This is a difference of six orders of magnitude or 1,000,000 times faster.

Supported Browsers and Caveats

Currently, the following browsers are auto-detected and managed:

  1. Chromium
  2. Firefox
  3. google-chromeAUR
  4. Midori
  5. Opera
  6. Opera-nextAUR
Note: Chromium actually keeps its cache directory separately from its browser profile directory. It is not within the scope of profile-sync-daemon to modify this behavior; users are encouraged to refer to the Chromium_Tips_and_Tweaks#Cache_in_tmpfs section of the main Chromium_Tips_and_Tweaks article for several work-arounds.

Setup and Installation

Profile-sync-daemonAUR is available for download from the AUR. Build it and install like any other package.

Edit /etc/psd.conf

Edit the included /etc/psd.conf defining which user(s) will have their profiles managed by psd.


# List users separated by spaces whose browser(s) profile(s) will get symlinked 
# and sync'ed to tmpfs.
# Do NOT list a user twice!
USERS="bar foo"
Note: At least one user must be defined.

Optionally uncomment the BROWSERS array and populate it with whichever browser(s) are to be sync'ed to tmpfs. If the BROWSERS array stays commented (default) then all supported browsers will be sync'ed.

Example: Let's say that both chromium and mirdori are installed but only chromium is to be sync'ed to tmpfs since the user keeps Midori as a backup browser and it is seldom used:

# List browsers separated by spaces to include in the sync. Useful if you do not
# wish to have all possible browser profiles sync'ed.
# Possible values are chromium, google-chrome, mozilla, midori, and opera
# Note that mozilla is the correct value for the firefox browser!
# If the following is commented out (default), then all available/supported 
# browsers will be sync'ed

Optionally redefine the location of the tmpfs mount to use for syncs. Do this in the VOLATILE variable. Note that for Arch Linux, the default value of "/tmp" should work just fine.

Using psd

The initial synchronization will occur when the daemon starts. Additionally, cron (if running) will call it to sync or update once per hour. Finally, psd will sync back a final time when it is called to stop.

Using SysVinit (Arch default)

Call the daemon to start, stop, or sync (restart) like any standard Arch daemon:

# rc.d <command> psd

It is highly recommended to start/stop the daemon at boot/shutdown. This is accomplished by adding psd to the DAEMONS array in /etc/rc.conf like so:

DAEMONS=(... @psd ...)

Using systemd

Users making use of Systemd may manage the service using the systemctl command. Start/stop the service using:

# systemctl start psd.service
# systemctl stop psd.service

Enable the psd daemon to start/stop at boot/shutdown (highly recommended) using:

# systemctl enable psd.service

Sync at More Frequent Intervals (Optional)

Note: This step is NOT required. psd will update once per hour on its own.

Users wishing to have syncs occur more frequently can simply add a line to the root crontab to call the sync function of psd like so:

# crontab -e

Example syncing all profiles being managed once every ten minutes:

 */10 * * * *     rc.d sync psd &> /dev/null


Post in the discussion thread with comments or concerns.