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 something similar.
>
> Yes, and that's fundamentally hard without creating races and still
> maintaining the desired ordering of locate output. updatedb.mlocate
> tries, and has to do a very complicated dance with chdir() back and forth.
> It runs into lots of icky cases and has to just silently ignore some errors
> (with associated races); the only winning move is not to play.
Unsorted output of locate, or updatedb.plocate not building the db
correctly? If the first, eg "apt-cache search locate" too gives poorly
sorted results. Following Unix philosophy by adding a tool ("| sort")
that does one thing well solves that cosmetic problem.
Cheers,
GSR
