On 2020-03-27 at 13:32:30, Christian Kastner wrote:
> On 24.02.20 09:49, Timo van Roermund wrote:
> > I see the same issue:
> >
> > Feb 23 16:22:06 hostname smbd[522826]: PAM unable to dlopen(pam_cap.so):
> > /lib/security/pam_cap.so: cannot open shared object file: No such file
> > or directory
I haven't seen this anymore after Feb. 23. So I assume it was some
temporary glitch indeed.
On 24.02.20 09:49, Timo van Roermund wrote:
> I see the same issue:
>
> Feb 23 16:22:06 hostname smbd[522826]: PAM unable to dlopen(pam_cap.so):
> /lib/security/pam_cap.so: cannot open shared object file: No such file
> or directory
> Feb 23 16:22:06 hostname smbd[522826]: PAM adding faulty
I see the same issue:
Feb 23 16:22:06 hostname smbd[522826]: PAM unable to dlopen(pam_cap.so):
/lib/security/pam_cap.so: cannot open shared object file: No such file
or directory
Feb 23 16:22:06 hostname smbd[522826]: PAM adding faulty module: pam_cap.so
This started after the upgrade of
On 11.02.20 17:32, Francois Marier wrote:
> I see the following in my logs:
>
> Feb 11 07:39:22 hostname systemd: PAM unable to dlopen(pam_cap.so):
> /lib/security/pam_cap.so: cannot open shared object file: No such file or
> directory
> Feb 11 07:39:22 hostname systemd: PAM adding faulty
Package: libpam-cap
Version: 1:2.31-1
Severity: normal
I see the following in my logs:
Feb 11 07:39:22 hostname systemd: PAM unable to dlopen(pam_cap.so):
/lib/security/pam_cap.so: cannot open shared object file: No such file or
directory
Feb 11 07:39:22 hostname systemd: PAM adding faulty
6 matches
Mail list logo