User Tools

Site Tools


linux:fedora_tips

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
linux:fedora_tips [2018/01/18 10:23]
jansen
linux:fedora_tips [2022/06/08 12:32]
jansen
Line 41: Line 41:
 ===== Performance issues ===== ===== Performance issues =====
 ---- ----
-Some applications are clearly designed for use by a single user on a single system, and some of this doesn't scale well to n users on m systems (something like n*m comes to mind). In other words, things come to a grinding halt, complicated even more by the lack of disk quota on the home disk, whereas $HOME is one of the few locations an application can count on to exist on any system. Here are some tips to get around that kind of problem.+Some applications are clearly designed for use by a single user on a single system, and some of this doesn't scale well to n users on m systems (something like n*m comes to mind). In other words, things come to a grinding halt, complicated even more by the lack of [[disk quota]] on the home disk, whereas $HOME is one of the few locations an application can count on to exist on any system. Here are some tips to get around that kind of problem.
  
 ===== Firefox, Chrome and other disk hogs ===== ===== Firefox, Chrome and other disk hogs =====
Line 66: Line 66:
 You can also check, if earlier versions of Gimp left behind their directories, and remove them if they exist. You can also check, if earlier versions of Gimp left behind their directories, and remove them if they exist.
  
-===== XDG basedir standards =====+===== Cache directory ; XDG basedir standards =====
 ---- ----
-A lot of programs are using the (relatively new) freedesktop XDG basedir setup, which puts configuration files in .config, cache in .cache and various data files of the application in .local  +A lot of programs are using the Freedesktop XDG basedir setup, which puts configuration files in .config, cache in .cache and various data files of the application in .local \\ 
-However, the data and cache parts can become quite big, causing two problems: quota usage on the home disk, and performance loss (since the home disk is remote, and this can cause lots of read and write access).  +However, the data and cache parts can become quite big, causing two problems: [[disk quota]] usage on the home disk, and performance loss (since the home disk is remote, and this can cause lots of read and write access).  
-Now the XDG standard provides a mechanism to move those files to another location, and we suggest users move them to one of their local data disks. We also provide a script that takes care of the environment setup, but selecting a location and moving the files is something you have to do yourself.  +Now the XDG standard provides a mechanism to move those files to another location, and we suggest users move them to one of their local data disks. We also provide a script [[sfinx-xdg]] that takes care of the environment setup, but selecting a location and moving the files is something you can do yourself. By default (2019-03-20) the cache is moved for all users to the local /data1, unless they set another location
-Follow these steps to get started:+ 
 +A quick solution (shown here just for the cache), is to move the cache to a data disk and link to that location: 
 + 
 +  mv ~/.cache /net/yourcomputer/data1/username/cache 
 +  ln -s /net/yourcomputer/data1/username/cache ~/.cache 
 + 
 +a more complete setup works like this:
  
   - close programs that may have files open in the XDG directories. This is especially important for Evolution (mail client).   - close programs that may have files open in the XDG directories. This is especially important for Evolution (mail client).
-  - Run 'sfinx-xdg' with the path where you want to store the files. Default is /data/$USER/xdg but if you want to be able to use it from other computers as well, /net/$HOSTNAME/data/$USER/xdg might be a better alternative. Or, on recent desktops where /data2 is a RAID1 disk, so guarded against disk failure, you may want to use /data2 in stead of /data. Or maybe you want it in another location altogether.If you only want to move the cache and not the data location, use sfinx-xdg --cacheonly /net/$HOSTNAME/data/$USER/xdg(or any other location that you prefer)+  - Run '[[sfinx-xdg]]' with the path where you want to store the files. Default is /data/$USER/xdg but if you want to be able to use it from other computers as well, /net/$HOSTNAME/data/$USER/xdg might be a better alternative. Or, on recent desktops where /data2 is a RAID1 disk, so guarded against disk failure, you may want to use /data2 in stead of /data. Or maybe you want it in another location altogether. If you only want to move the cache and not the data location, use sfinx-xdg --cacheonly /net/$HOSTNAME/data/$USER/xdg (or any other location that you prefer)
   - If the specified directory doesn't exist yet, it will be created along with subdirectories for cache and data. Also created is a file .sfinx-xdgrc which contains the path, and this will be used on subsequent logins to set the environment. The RC file will also contain settings that determine whether you want to redirect cache, data or both.   - If the specified directory doesn't exist yet, it will be created along with subdirectories for cache and data. Also created is a file .sfinx-xdgrc which contains the path, and this will be used on subsequent logins to set the environment. The RC file will also contain settings that determine whether you want to redirect cache, data or both.
-  - Set the environment in your current shell, and move the existing files to their new locations: +  - If your setup includes moveing application data, set the environment in your current shell, and move the existing files to their new locations (nothing in cache is worth moving, so remove it if you like)
-  eval `sfinx-xdg` + 
-     mv ~/.cache/* $XDG_CACHE_HOME/+     eval `sfinx-xdg`
      mv ~/.local/share/ $XDG_DATA_HOME/      mv ~/.local/share/ $XDG_DATA_HOME/
 + 
   - Log out, and on your next login, all programs should find their data and cache in the new location.   - Log out, and on your next login, all programs should find their data and cache in the new location.
   - Witness the increase in performance, especially in the Google Chrome browser and the Evolution mail client.   - Witness the increase in performance, especially in the Google Chrome browser and the Evolution mail client.
Line 117: Line 124:
   systemctl --user disable --now evolution-addressbook-factory   systemctl --user disable --now evolution-addressbook-factory
  
 +===== ClipIt clipboard manager =====
 +The ClipIt tool provides a history of cut and paste actions. Very useful... If it works. And unfortunately, it often doesn't work (mostly related to damaged history files, or insufficient disk quota at some point).
 +So, it you don't require the feature, or if it simply blocks any cut & paste action in your session, just exit the program or remove it from your session startup applications.
 +  - Exit the program: find the ClipIt icon in the system tray. It looks like a clipboard with a document next to it. \n Right-click on the icon and choose "quit"
 +  - If the icon is not there, try the command: 'pkill clipit'
 +  - To permanently remove it from your session, go to the system settings in the main desktop menu, choose "startup application" and move the clider next to "ClipIt"
  
linux/fedora_tips.txt · Last modified: 2022/06/08 12:32 by jansen