Date: Tue, 01 Oct 2024 12:36:43 +0100 From: Jamie Landeg-Jones <jamie@catflap.org> To: kevans@FreeBSD.org, jamie@catflap.org, freebsd-current@FreeBSD.org Subject: Re: weekly locate error Was: September 2024 stabilization week Message-ID: <202410011136.491BahKt023300@donotpassgo.dyslexicfish.net> In-Reply-To: <21c4125f-0ac0-46f4-9f5c-9f14a3e7e397@FreeBSD.org> References: <ZvEgC9ak7paxygYw@cell.glebi.us> <ZvRze1gldJTCvjir@cell.glebi.us> <Zvh-8cMF_HtOJ3uu@int21h> <Zvrp25zS9thDe3ak@cell.glebi.us> <3313f951-4f9e-4298-bbd8-f82c5a15a0e3@protected-networks.net> <ZvsTQu_LQFHs1lnN@cell.glebi.us> <ZvsX9qOI_bSAL7Mj@int21h> <f01f6af0-d9f2-482c-b2b0-1d86937c86fa@FreeBSD.org> <202410010036.4910aIoW095390@donotpassgo.dyslexicfish.net> <21c4125f-0ac0-46f4-9f5c-9f14a3e7e397@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kyle Evans <kevans@FreeBSD.org> wrote: > Yes, my proposal is that it stops doing that and we teach updatedb to > handle the priv-dropping instead, so that you get the same behavior no > matter how you execute it. Ahhh OK, I get you now. sorry, I musunderstood, I thought you meant the current "periodic" method runs the filesystem walk as root, but when you said "if someone really wants to complain that they can't document all filenames on the system.", i guess you were referring to those who may call /usr/libexec/locate.updatedb directly as root. For what it's worth, in addition to the periodic job, I do actually run a less frequent privileged direct run of /usr/libexec/locate.updatedb (with the output in a suitably locked directory!). This proposed change wouldn't be an issue to me, but as a data point, there may be quite a few others who do so too. Cheers, Jamie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202410011136.491BahKt023300>