On Tue, Dec 08, 2020 at 01:04:07AM +0100, GSR wrote: > And the ulimit line is missing, so when testing manually it fails with > ---8<--- > /some/dir/somewhere: Too many open files > Hint: Try `ulimit -n 8192' or similar (current limit is 4096). > --->8---
That's odd; it should do setrlimit() itself at startup (LimitNOFILE= in the systemd unit is just to set the hard limit). How can ulimit in the shell succeed but setrlimit() fail? > When run for personal databases the solution must come from the > binary, as users will not be able to raise limit beyond the hard > number. updatedb isn't privileged, so it's no more able to raise the hard limit than the user is. /* Steinar */ -- Homepage: https://www.sesse.net/
