![]() ![]() The same recovery features psd uses in its default mode are also active when running in overlayfs mode. The magic is in how the overlay mount only writes out data that has changed rather than the entire profile. When used with psd, a reduced memory footprint and faster sync operations can be realized. See the official website for available packages, dependencies, and installation instructions FAQĪ1: Overlayfs is a simple union filesystem mainlined in the Linux kernel version 3.18.0. Several distros provide an official package or user-maintained option to install psd. Since psd is just a bash script with a systemd service, it should run on any flavor of Linux running systemd. Other solutions may exist for other browsers but documenting them all here is out of scope. One also needs to adjust the IsRelative flag like so: Exiting.Ī proper work around for firefox is to simply edit ~/.mozilla/firefox/profiles.ini defining the canonical path there. Please make the browser profile a live directory and try again. home/facade/.mozilla/firefox/fault appears to be a symlink but these are not supported. Running psd in preview mode will end in an error informing you of this: $ psd p Tmpfs dir: /run/user/1000/facade-chromium Sync target: /home/facade/.config/chromium Psd will manage the following per /home/facade/.config/psd/.psd.conf settings: It will also provide useful information such as profile size, paths, and if any recovery snapshots have been created. The preview option can be called to show users exactly what psd will do/is doing based on the entries in the config file. The user copy ($XDG_CONFIG_HOME/psd/psd.conf) will need to be diffed against it. NOTE: occasionally, updates/changes are made to the default config file (/usr/share/psd/psd.conf) upstream. Optionally define the number of crash-recovery snapshots to keep.Optionally disable the use of crash-recovery snapshots (not recommended).If none are defined, the default is all detected browsers. Optionally define which browsers are to be managed in the BROWSERS array.This can help in the event that the system does not properly wake up. Optionally have psd resync to the filesystem prior to a sleep call.See the FAQ below for additional details. The user will require no password sudo rights to /usr/bin/psd-overlay-helper to use this option and the kernel must support overlayfs version 22 or higher. Optionally enable the use of overlayfs to improve sync speed and to use a smaller memory footprint.NOTE: edits made to the config file while psd is active will be applied only after the service has been restarted. $XDG_CONFIG_HOME/psd/psd.conf (referred to hereafter as "the config file") contains all user managed settings. It is not within the scope of profile-sync-daemon to modify this behavior users wishing to relocate this directory, may refer to the following url for several work-arounds: Setup *Note that some browsers such as Chrome/Chromium, Firefox (since v21), Midori, and Rekonq actually keep their cache directories separate from their browser profile directory. are relocated into tmpfs (RAM disk), the corresponding I/O associated with using the browser is also redirected from the physical disc to the RAM, thus reducing wear to the physical disc and improving browser responsiveness. Since the profile/profiles, browser cache*, etc. Reduced wear to physical discs (particularly SSDs).Completely transparent user experience.Additionally, psd features several crash-recovery features. This is accomplished by an innovative use of rsync to maintain synchronization between a tmpfs copy and media-bound backup of the browser profile/profiles. Profile-sync-daemon (psd) is a tiny pseudo-daemon designed to manage browser profile/profiles in tmpfs and to periodically sync back to the physical disc (HDD/SSD). If we run the sync a second time, rsync won’t detect any files to sync.Symlinks and syncs browser profiles to RAM (tmpfs) thus reducing HDD/SSD calls and speeding up browsers. Sent 358 bytes received 111 bytes 938.00 bytes/sec If we’re sure these files are the ones that we want to sync, we can remove the -n flag and run the actual sync: $ rsync -havu dir1/ dir2/ Let’s run the command and check the output: $ rsync -havun dir1/ dir2/ Therefore, when using rsync, doing a dry run is an important first step. It’s useful to see what we’ll be doing before actually running the command.īy doing a dry run ( -n) before doing an actual sync operation, we can catch user errors that may cause data loss. A dry run only simulates the sync and lists the output without actually syncing anything. This will skip files that are newer on the receiver. ![]() The -v flag increases verbosity to print out the details of what is done. (-D) preserve devices and special files. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |