So updatedb(1) from slocate-3.1 accidentally indexes Poetterings's tmpfs and all media mounted below /run/media. I don't think, the latter was intended behaviour, because /mnt and /media are listed explicitly.

Do not question the Pottering!
Just kidding. Thank you for this post, I've learned something new about updatedb.
Meanwhile, I'm still enjoying the crap out of 13.37. Once I figure out how to sufficiently de-Potterize 14.0, I might upgrade to it on my main system (already bought the DVD).

Thanks. I usually keep stuff (*cough *cough) that I wouldn't want the kids to see on a separate drive. Sometimes that's attached at night. I wouldn't like the contents of that indexed !

Yep, it does look like /run needs to be added. My PRUNEFS= line has tmpfs on it, but while this stops updatedb from indexing /run itself, it doesn't stop updatedb from traversing /run into any filesystems mounted under it (such as those under /run/media). Well spotted.


@Mark,

slocate will only list files that are both currently accessible, and readable by the user running the query. So, unless your kids have root access and are knowledgeable enough to try and run something like 'strings' against /var/lib/slocate/slocate.db then daddy's nocturnal activities involving "stuff" should remain undetected.

@GazL - thanks for that tip. I was under the impression that the slocate database remained in force until the next running of the updatedb command - ie approx 4:00 am daily. 13 years running Linux and I still learn new stuff !