Dev Stack Source

Answer : It can be killed with: sudo killall updatedb.mlocate Or: sudo kill -9 <PID> It runs every day by cron. Disable it with: sudo chmod -x /etc/cron.daily/mlocate And if you want to re-enable it: sudo chmod +x /etc/cron.daily/mlocate I did not want to totally eliminate the process but I did want to make it happen less frequently so I worked out how to set it to run weekly instead of daily. This is based on the accepted answer above but probably best listed as its own answer as it's not disabling it. That said... It's rather simple and appears to work just fine. sudo chmod -x /etc/cron.daily/mlocate sudo cp /etc/cron.daily/mlocate /etc/cron.weekly/mlocate sudo chmod +x /etc/cron.weekly/mlocate The first one disables the cron job. The second moves it to the weekly tasks. The third command sets the permissions so that it is enabled. Daily, hourly, weekly, and monthly are all options. I never used locate , so I removed it. sudo dpkg -P mlocate Se...

Answer : I will just add to Gilles' answer by saying that although you may use “ cp , rsync , etc.” to transfer your read-only subvolumes / snapshots, you may also send and store the subvolumes as btrfs streams using the btrfs send command. The btrfs Wiki mentions the following use: # btrfs subvolume snapshot -r / /my/snapshot-YYYY-MM-DD && sync # btrfs send /my/snapshot-YYYY-MM-DD | ssh user@host btrfs receive /my/backups # btrfs subvolume snapshot -r / /my/incremental-snapshot-YYYY-MM-DD && sync # btrfs send -p /my/snapshot-YYYY-MM-DD /my/incremental-snapshot-YYYY-MM-DD | ssh user@host btrfs receive /backup/home but you may also just save the streams for future use: # btrfs subvolume snapshot -r / /my/snapshot-YYYY-MM-DD && sync # btrfs send /my/snapshot-YYYY-MM-DD | ssh user@host 'cat >/backup/home/snapshot-YYYY-MM-DD.btrfs' # btrfs subvolume snapshot -r / /my/incremental-snapshot-YYYY-MM-DD && sync # btrfs send -p /my...