Bug#1004083: plocate: stops with misleading error on pruned filesystem

2022-01-30 Thread Steinar H. Gunderson
On Sun, Jan 30, 2022 at 01:42:54PM -0700, Kevin Locke wrote: > Sure thing. After re-creating the broken CIFS mount on /mnt, I ran: > > updatedb -o /tmp/plocate.db > locate -d /tmp/plocate.db debian_version Great! Thanks for testing; I'll probably push out a new version shortly. /* Steinar */

Bug#1004083: plocate: stops with misleading error on pruned filesystem

2022-01-30 Thread Kevin Locke
On Sun, 2022-01-30 at 21:16 +0100, Steinar H. Gunderson wrote: > On Sun, Jan 30, 2022 at 07:25:55PM +0100, Steinar H. Gunderson wrote: >> Yes, I wonder if this is the best fix for this specific issue. >> If there's an error, there's no performance issue, since the alternative >> is total failure;

Bug#1004083: plocate: stops with misleading error on pruned filesystem

2022-01-30 Thread Steinar H. Gunderson
On Sun, Jan 30, 2022 at 07:25:55PM +0100, Steinar H. Gunderson wrote: > Yes, I wonder if this is the best fix for this specific issue. > If there's an error, there's no performance issue, since the alternative > is total failure; we can check /proc/mounts before deciding to crash out > or nt.

Bug#1004083: plocate: stops with misleading error on pruned filesystem

2022-01-30 Thread Steinar H. Gunderson
On Sun, Jan 30, 2022 at 11:10:00AM -0700, Kevin Locke wrote: > I think the behavior is understandable in both of the above cases, > although it's unfortunate that a flakey mount on an excluded > filesystem at an otherwise always empty directory causes updatedb to > fail entirely. I'm not sure if

Bug#1004083: plocate: stops with misleading error on pruned filesystem

2022-01-30 Thread Kevin Locke
Thanks for the thoughtful response! On Sun, 2022-01-30 at 18:47 +0100, Steinar H. Gunderson wrote: > On Thu, Jan 20, 2022 at 08:05:14AM -0700, Kevin Locke wrote: >> 2. The error occurred on a CIFS filesystem, which is excluded by >>PRUNEFS in /etc/updatedb.conf. Presumably it should be

Bug#1004083: plocate: stops with misleading error on pruned filesystem

2022-01-30 Thread Steinar H. Gunderson
On Thu, Jan 20, 2022 at 08:05:14AM -0700, Kevin Locke wrote: > It turns out this the failure was due to a network issue which > prevented contacting the host for the CIFS mount on /mnt. However, > this presents several issues that might be worth addressing: > > 1. The error message contains the

Bug#1004083: plocate: stops with misleading error on pruned filesystem

2022-01-20 Thread Kevin Locke
Package: plocate Version: 1.1.14-1 Severity: normal Dear Maintainer, On a machine with a CIFS mount on /mnt, plocate-updatedb.service failed and updatedb.plocate printed: /: Host is down Running updatedb.plocate -v printed: //initrd.img.old //vmlinuz.old //mnt //root //vmlinuz //sys //bin