My cron is running this
https://github.com/openbsd/src/blob/master/etc/weekly
and it fails with the given error message.
If I edit the file as I said, then it works.
This is what I am doing, and I am surprised it fails for me and not for you.
Sent from Proton Mail Android
-------- Original Message --------
On 5/17/25 18:48, Ingo Schwarze <schwa...@usta.de> wrote:
> Hello Otto,
>
> On Saturday, May 17th, 2025 at 5:30 PM, otto.cooper wrote:
>
> > To avoid indexing large mounted volumes, as well as to focus the
> > locate database, I re-refined SEARCHPATHS in /etc/locate.rc:
> >
> > SEARCHPATHS="/usr /var"
> >
> > However, /usr/libexec/locate.updatedb ignores the configuration file.
>
> On Saturday, May 17th, 2025 at 5:52 PM, otto.cooper wrote:
>
> > If I call /usr/libexec/locate.updatedb directly, the problem
> > does not occur. When called by /etc/weekly, the problem occurs.
>
> I cannot reproduce, it works as documented for me:
>
> # grep ^SEARCHPATHS /etc/locate.rc
> SEARCHPATHS="/etc"
> # /bin/sh /etc/weekly
> # locate locate
> /etc/locate.rc
> # vi /etc/locate.rc
> # diff -u /usr/src/etc/locate.rc /etc/
> # /bin/sh /etc/weekly
> # locate locate | wc -l
> 964
>
> I suspect you are doing something wrong, but it is not apparent to me
> what that might be.
>
>
> otto.cooper wrote on Sat, May 17, 2025 at 04:12:20PM +0000:
>
> > To speed-up the solution, I edited /etc/weekly:
> >> echo "${UPDATEDB} --fcodes=- --searchpaths=\"/usr /etc\"" | \
> > Considering that a generic system may have large mounted storage
> > devices, I think that SEARCHPATHS ought to be narrowed to relevant
> > folders by default.
>
> I disagree. I want stuff like /home and /var/www indexed by default.
> If you have special needs to exclude something on a specific machine,
> means for doing so are already provided via /etc/locate.rc
> as documented in locate.updatedb(8).
>
> As a side note, sending four mails for a single problem report is
> not appreciated because it wastes time. In the future, please
> make sure to first analyze the potential problem as well as you
> can, then send *one* message containing all the information in
> an organized manner.
>
> Yours,
> Ingo
>
>
