On Wed, 2021-08-18 at 18:59 +0200, Francis.Montagnac@xxxxxxxx wrote: > > Hi. > > On Wed, 18 Aug 2021 16:34:50 +0100 Patrick O'Callaghan wrote: > > > On Wed, 2021-08-18 at 15:25 +0000, Jan-Henrik Sorsimo via users > > wrote: > > > > I took a look at the service unit file > > > (/usr/lib/systemd/system/mlocate-updatedb.service). It has some > > > sandboxing features set. When I set the value of "ProtectSystem" > > > to > > > either "false" or "strict", a manual run of the service does > > > include > > > the files under /usr in the database. Other options result in the > > > behavior mentioned. > > > > I can't see what sense this makes. That setting is supposed to > > > just > > > cover what gets mounted read-only. A systemd bug? > > I see the same behavior since using a btrfs subvol for / > > Commenting PRUNE_BIND_MOUNTS = "yes" in /etc/updatedb.conf solves > this > problem. > > > I have the inverse problem, i.e. locate will find files in the root > > filesystem but not in my /home. > > May be the same cause ... Looks like it. My /home is a BTRFS subvolume. Extraordinary that this hasn't been fixed, given that F34 uses BTRFS by default. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
