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 it might be worth the effort to check > /proc/mounts or statfs(2) on stat(2) failure (for certain error > codes?), or to consider whether the directory is currently empty in > the database, or to skip it without discarding previous entries, or > something else. I'll defer to your judgement.
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. /* Steinar */ -- Homepage: https://www.sesse.net/
