Re: Tuning SEARCHPATHS in locatedb

On Sat, May 17, 2025 at 8:57 AM otto.cooper wrote: > If I call /usr/libexec/locate.updatedb directly, the problem does not occur. > > When called by /etc/weekly, the problem occurs. Well, what does /etc/weekly do that you aren't when you run it manually? /etc/weekly runs it as user 'nobody'; is

Re: Tuning SEARCHPATHS in locatedb

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

Re: Tuning SEARCHPATHS in locatedb

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. --OC Sent with Proton Mail se

Tuning SEARCHPATHS in locatedb

The file /usr/libexec/locate.updatedb defines SEARCHPATHS as "/". The same file defines a way to configure its operations, by reading LOCATE_CONFIG="/etc/locate.rc", from which SEARCHPATHS can be re-refined in locate.rc or specified as --searchpaths. To avoid indexing large mounted volumes, as

Re: Tuning SEARCHPATHS in locatedb

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

Re: % in crontab(5)s [Was: /bin/sh and RANDOM documention error?]

Thanks everyone who found the solution. The issue was indeed the unescaped % in the crontab entry. I had missed that while looking into the problem and mistakenly concluded that RANDOM was somehow at fault. Note: The rest of the discussion around what lead to the issue and my original post is

Re: Tuning SEARCHPATHS in locatedb

If I call /usr/libexec/locate.updatedb directly, the problem does not occur. When called by /etc/weekly, the problem occurs. Sent with Proton Mail secure email. On Saturday, May 17th, 2025 at 5:37 PM, otto.cooper wrote: > Side note > > old minimal: > > > SEARCHPATHS="/usr /var" > > > n

Re: Tuning SEARCHPATHS in locatedb

Side note old minimal: > SEARCHPATHS="/usr /var" new minimal: > SEARCHPATHS="/usr /etc" because /etc/weekly tests itself. Sent with Proton Mail secure email. On Saturday, May 17th, 2025 at 5:30 PM, otto.cooper wrote: > The file /usr/libexec/locate.updatedb defines SEARCHPATHS as "/". > The

Re: Perl XML::Feed

On Thu, 15 May 2025 19:29:00 -0400 Jon Fineman wrote: > I am trying to install XML::Feed on 7.7 GENERIC.MP#625. This I believe > relies upon XML::LibXML. It looks like I am getting unit test errors > for LibXML. > > I also installed libxml-2, p5-libxml. Alien::Libxml2 was already installed >

Re: % in crontab(5)s [Was: /bin/sh and RANDOM documention error?]

fischer+o...@lavielle.com (Mike Fischer), 2025.05.16 (Fri) 17:53 (CEST): > > Am 16.05.2025 um 17:33 schrieb Jan Stary : > >>> How exactly are you using RANDOM in a crontab, > >> * * * * * time $((RANDOM % 60));/home/username/bin/script.sh > > That doesn't make any sense: do you mean sleep(1) instea

Re: Relayd httpd headers Injection

kihagurugath...@gmail.com (Kihaguru Gathura), 2025.05.16 (Fri) 09:54 (CEST): > What is the way to inject http headers in httpd for static content? found some snippets for you in a live relayd.conf: match response header remove "Server" match response header set "Connection" value "close" Marcus