On Mon, Apr 18, 2022 at 04:50:58PM -0400, James Cloos wrote:
> SG> This was fixed in plocate 1.1.12. ... Which version are you running?
> as i mentioned the sbc has buster, so:
>
> ii plocate1.1.8-2~bpo10+1 armhfmuch faster locate
And also, a very old kernel?
/* Steinar */
--
oh. is that all it is. ...
so the reporter's issue is certainly different.
SG> This was fixed in plocate 1.1.12. ... Which version are you running?
as i mentioned the sbc has buster, so:
ii plocate1.1.8-2~bpo10+1 armhfmuch faster locate
-JimC
--
James Cloos
On Mon, Apr 18, 2022 at 12:32:20AM -0400, James Cloos wrote:
> the strace output ends with:
>
> openat(AT_FDCWD, "/var/lib/plocate/", O_WRONLY|O_LARGEFILE|O_TMPFILE, 0640)
> = -1 EISDIR (Is a directory)
>
> i've only seen it on arm32 buster, though.
It shouldn't end there, though; if the
> "SG" == Steinar H Gunderson writes:
SG> If so, I don't understand why running updatedb manually doesn't do anything.
SG> Perhaps there are multiple issues in play on the same bug number.
*perhaps* he gets something similar to what i see on one arm32 buster sbc:
updatedb exits
Yes. Once I've figured out what the problem is, I'll file another bug
report.
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
On Sun, 2022-04-17 at 23:27 +0200, Steinar H. Gunderson wrote:
> On Sun, Apr 17, 2022 at 04:39:30PM -0400, Ron Murray wrote:
> >
On Sun, Apr 17, 2022 at 04:39:30PM -0400, Ron Murray wrote:
>Sorry, perhaps I wasn’t too clear. Running updatedb manually works fine.
>I just had to do it again. I think the only issue is the auto update.
I think that should be on a different bug, then.
/* Steinar */
--
Homepage:
Ah.
Sorry, perhaps I wasn’t too clear. Running updatedb manually works fine. I
just had to do it again. I think the only issue is the auto update.
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
> On Apr 17, 2022, at 16:14, Steinar H. Gunderson wrote:
>
On Sun, Apr 17, 2022 at 04:07:21PM -0400, Ron Murray wrote:
> I think the problem is that the cron.daily plocate job isn't being run.
> I'd suspect the systemd timer doesn't work, but I'm not sure. I'll hack
> the cron.daily/plocate script to save some diagnostic information, and
> perhaps that'll
I think the problem is that the cron.daily plocate job isn't being run.
I'd suspect the systemd timer doesn't work, but I'm not sure. I'll hack
the cron.daily/plocate script to save some diagnostic information, and
perhaps that'll help.
Thanks,
.Ron
--
Ron Murray
PGP Fingerprint: 4D99
On Sat, Apr 09, 2022 at 07:50:09PM -0400, Ron Murray wrote:
>Steinar, you may be right about problems with the upgrade. I started
> looking into this earlier today because 'locate' couldn't find files
> that I knew were present in the filesystem. Based on what you said, I
> checked plocate.db
Package: plocate
Version: 1.1.15-2
Followup-For: Bug #1009143
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Steinar, you may be right about problems with the upgrade. I started
looking into this earlier today because 'locate' couldn't find files
that I knew were present in the filesystem.
11 matches
Mail list logo