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; we can check /proc/mounts before deciding to crash out
>> or nt.
>
> I've pushed a change for this to upstream git; are you in a position to try
> it out?
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
I can confirm that with 5aea022 updatedb prints
/mnt: Host is down
then exits with code 1 (and does not create /tmp/plocate.db). With
e734063 updatedb exits with code 0 and no error is printed. locate
prints /etc/debian_version as expected.
Those both seem like great improvements to me. Thank you for the
quick response and fixes!
Cheers,
Kevin
