Date: Mon, 30 Sep 2024 14:25:49 -0400 From: Michael Butler <imb@protected-networks.net> To: Gleb Smirnoff <glebius@freebsd.org>, void <void@f-m.fm>, freebsd-current@freebsd.org Subject: Re: weekly locate error Was: September 2024 stabilization week Message-ID: <3313f951-4f9e-4298-bbd8-f82c5a15a0e3@protected-networks.net> In-Reply-To: <Zvrp25zS9thDe3ak@cell.glebi.us> References: <ZvEgC9ak7paxygYw@cell.glebi.us> <ZvRze1gldJTCvjir@cell.glebi.us> <Zvh-8cMF_HtOJ3uu@int21h> <Zvrp25zS9thDe3ak@cell.glebi.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/30/24 14:11, Gleb Smirnoff wrote: > On Sat, Sep 28, 2024 at 11:10:57PM +0100, void wrote: > v> I have found that *only* on arm64, locate errors like so: > v> > v> # sh /etc/periodic/weekly/310.locate > v> > v> Rebuilding locate database: > v> install: /var/db/INS@ArwCNx: Permission denied > v> > v> However, if it's run like this: > v> > v> # sh /usr/libexec/locate.updatedb > v> > > > WARNING > v> > > > Executing updatedb as root. This WILL reveal all filenames > v> > > > on your machine to all login users, which is a security risk. > v> > v> it exits normally. > v> > v> Moving /var/db/locate.database aside makes no difference. The problem doesn't > v> happen on amd64 arch, same 6e414739fc95. > > I also observe this and on amd64, so this is not arch specific. > > Not sure this appeared in the latest stabilization cycle, could have been > introduced earlier. > > Manual run of the periodic job doesn't reproduce the problem :( Backing out commit f62c1f3f8e91c78d402e1db4e518e4899a4ba2b9 resolves it for me, Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3313f951-4f9e-4298-bbd8-f82c5a15a0e3>