In my current setup, I have two machines serverA and serverB in different geographical areas. serverA has a limited amount of persistent memory (~256GB), while serverB can be considered to have enough that I will never use it all up (several TB). serverA has a directory /data which is an NFS share from serverB, and also has CacheFiles enabled. This setup achieves the following: 1. replication: if serverA's disk die, I can still recover the data from serverB 2. unlimited memory: I am not limited by serverA's small amount of persistent memory 3. fast access to data: the content of /data that is in the cache (basically the most recently accessed 200GB) can be accessed without a round-trip on the network Note that a simple backing-up setup would not achieve 2. I'd like to achieve 1., 2. and 3. but also the following: 4. robustness: if serverB goes down temporarily, serverA can still work with the data that's been cached, without me having to manually intervene on serverA 5. encryption: /data is encrypted by serverA, so that someone with access to serverB cannot access the data I'm mostly interested in 4. and 5. would only be a bonus. Here are my questions: - I suppose CacheFiles does not achieve 4., is this correct? - What are the simplest setups that would allow me to achieve 1., 2., 3. and 4., and possibly also 5.?

In Debian 12, the following command is run weekly: start-stop-daemon --start --pidfile /dev/null --startas /usr/bin/mandb --oknodo --chuid man -- --quiet which generates man caches in /var/cache/man But looking in that directory, I see all possible languages are being generated: ... ./zh_CN ./zh_CN/cat1 ./zh_CN/cat5 ./zh_CN/cat8 ./zh_CN/index.db ./zh_TW ./zh_TW/cat1 ./zh_TW/cat5 ./zh_TW/cat8 ./zh_TW/index.db I have language set to English, How do I prevent nonsense languages being generated?

What should we keep in mind when using CACHEDIR.TAG and .nobackup? Are these synonyms, or should we expect that programs handle these differently?

I'm about to back up some parts of my filesystem, including my home directory. I'm looking at $HOME/.cache, and wondering what I should do with it. I know that it's safe to just delete it altogether , but I also notice that most of the space is taken up by the web browser cache. So - of course not deleting caches meaning less time to recreate them, but is there some significant benefit which might make it worth it to keep some of the subdirectories of $HOME/.cache and just delete the browser cache (chromium and mozilla in my case)?

I have Anything-sync-daemon ("asd") installed and minimally configured according to this page: Anything-sync-daemon - ArchWiki Running asd p gives the following output: Anything-sync-daemon v5.85 on Arch Linux Systemd service is currently active. Systemd resync service is currently active. Overlayfs technology is currently inactive. Asd will manage the following per /run/asd.conf settings: owner/group id: myuser/1000 target to manage: /home/myuser/.cache sync target: /home/myuser/.cache-backup_asd tmpfs target: /tmp/asd-myuser/home/myuser/.cache dir size: 3.3G recovery dirs: none Executing cat /etc/asd.conf shows everything at default values except WHATTOSYNC: WHATTOSYNC=( '/home/myuser/.cache' ) # The default is to save the most recent 5 crash recovery snapshots. #BACKUP_LIMIT=5 The BACKUP_LIMIT is the default as shown above. systemctl list-timers shows: Mon 2018-02-05 19:20:13 EST 53min left Mon 2018-02-05 18:20:13 EST 6min ago asd-resync.timer asd-resync.service How do I tell asd to make backup snapshots?