On Fri, Dec 11, 2020 at 12:07:26AM +0100, GSR wrote:
> The cron script still not installed as executable, which is required
> by run-parts.
Thanks, I'll try to remember next upload.
> Unsorted output of locate, or updatedb.plocate not building the db
> correctly? If the first, eg "apt-cache
Version: 1.1.2-2
The cron script still not installed as executable, which is required
by run-parts.
Hi,
se...@debian.org (2020-12-10 at 0107.36 +0100):
> On Thu, Dec 10, 2020 at 12:58:09AM +0100, GSR wrote:
> > The solution I meant is "try working with less concurrently opened
> > files" or
On Thu, Dec 10, 2020 at 12:58:09AM +0100, GSR wrote:
> The solution I meant is "try working with less concurrently opened
> files" or something similar.
Yes, and that's fundamentally hard without creating races and still
maintaining the desired ordering of locate output. updatedb.mlocate
tries,
Hi,
se...@debian.org (2020-12-08 at 0109.08 +0100):
> 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
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()
Package: plocate
Version: 1.1.1-2
Followup-For: Bug #976427
Hi,
ow...@bugs.debian.org (2020-12-07 at 1009.05 +):
> plocate (1.1.1-2) unstable; urgency=medium
> .
>* Install a new /etc/cron.daily/plocate, for non-systemd users;
> based on work by GSR, which based it on the mlocate
6 matches
Mail list logo
