Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Sep 2024 15:16:27 +0000
From:      Gary Jennejohn <garyj@gmx.de>
To:        freebsd-current@freebsd.org
Subject:   Re: September 2024 stabilization week
Message-ID:  <20240929171627.1310f245@ernst.home>
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>

index | next in thread | previous in thread | raw e-mail

On Sun, 29 Sep 2024 10:21:57 -0400
Michael Butler <imb@protected-networks.net> wrote:

> On 9/28/24 18:10, void wrote:
>
> > I have found that *only* on arm64, locate errors like so:
> >
> > # sh /etc/periodic/weekly/310.locate
> >
> > 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
>

I just saw this error on my amd64 system also.  But /var/db/locate.database
was updated and I could use locate w/o a problem.

But I must say that I'm not running the most recent version of the source.
The source I installed is about three days behind.

--
Gary Jennejohn


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240929171627.1310f245>