Date: Sun, 29 Sep 2024 09:42:17 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Michael Butler <imb@protected-networks.net> Cc: <freebsd-current@FreeBSD.org>, <sjg@juniper.net> Subject: Re: September 2024 stabilization week Message-ID: <88021.1727628137@kaos.jnpr.net> In-Reply-To: <d0eb0b05-a207-4561-8419-95e03ffba065@protected-networks.net> References: <ZvEgC9ak7paxygYw@cell.glebi.us> <ZvRze1gldJTCvjir@cell.glebi.us> <Zvh-8cMF_HtOJ3uu@int21h> <d0eb0b05-a207-4561-8419-95e03ffba065@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Butler <imb@protected-networks.net> wrote: > > I have found that *only* on arm64, locate errors like so: > > > > # sh /etc/periodic/weekly/310.locate This runs /usr/libexec/locate.updatedb as nobody and ensures that /var/db/locate.database exists and is owned by nobody, but /var/db itself is root:wheel and 755 so the error from install does not seem surprising. Though that begs the question of how this ever works ;-) > > > > Rebuilding locate database: > > install: /var/db/INS@ArwCNx: Permission denied > > > > However, if it's run like this: > > > > # sh /usr/libexec/locate.updatedb > >>>> WARNING > >>>> Executing updatedb as root. This WILL reveal all filenames > >>>> on your machine to all login users, which is a security risk. > > > > it exits normally. > > > > Moving /var/db/locate.database aside makes no difference. The problem > > doesn't > > happen on amd64 arch, same 6e414739fc95. > > This happens on all my amd64 -current installs. > > It seems to have started with commit > f62c1f3f8e91c78d402e1db4e518e4899a4ba2b9 > > Michael >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?88021.1727628137>