Martin Bastien
8ef4eb24a2
The stock Arch updatedb.conf interacts badly with Omarchy's Btrfs layout in both directions: - Snapper snapshots under /.snapshots are nested subvolumes reached by plain directory traversal, so updatedb indexes the entire system once per snapshot. On machines that accumulated snapshots this means multi-hour updatedb runs at full CPU, gigabytes of RAM, and a multi-gigabyte plocate.db (observed: 18 GB db, 7.5 h runs at 96% CPU with 592 snapshots; 43 MB and ~1 min after the fix). - PRUNE_BIND_MOUNTS="yes" treats Btrfs subvolume mounts like /home as bind mounts, so locate finds nothing in home directories at all. Configure updatedb.conf at install time and migrate existing installs, then rebuild the index in the background. Both settings are matched tolerantly and appended when absent, so a hand-edited updatedb.conf is fixed rather than silently skipped.
10 lines
487 B
Bash
10 lines
487 B
Bash
run_logged "$OMARCHY_INSTALL/config/theme-system.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/increase-lockout-limit.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/lockscreen-pam.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/fix-powerprofilesctl-shebang.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/docker.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/snapper.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/locate.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/enable-services.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/firewall.sh"
|