Francis,
On Sat, 2021-01-09 at 16:23 +0100, francis.montag...@inria.fr wrote:
> Hi.
> On Fri, 08 Jan 2021 11:59:37 -0500 "Michael H. Warfield" wrote:
> > My level of confidence is growing. I think you hit the nail square
> > on
> > the head. The nsswitch.com problem may have been the issue. B
Hi.
On Fri, 08 Jan 2021 11:59:37 -0500 "Michael H. Warfield" wrote:
> My level of confidence is growing. I think you hit the nail square on
> the head. The nsswitch.com problem may have been the issue. But the
> cause may yet still be elsewhere. That file is owned by glibc. I'll
> file a bu
This MAY be related to this bug, I'm not sure how... Symptomatically,
it would make sense. Not sure of the causal link though...
https://github.com/systemd/systemd/issues/13432
On Fri, 2021-01-08 at 11:59 -0500, Michael H. Warfield wrote:
> Ed, et al...
>
> [Excuse the top posting but this is
Ed, et al...
[Excuse the top posting but this is just a prelim report]
Still too early to say for certain but...
Since taking your advice and eliminating that "resolve
[!UNAVAIL=return]" stanza from nsswitch.conf, I have only had one
failure in the afflicted systems and that was due to a hardwar
