For both it would be nice to see the logs, but since you were modifyin
---will try to get sir. They are just so hard to clean due to the
level info, which is GOOD, just hard to sed out stuff
On Mon, Jul 23, 2018 at 2:10 PM, Jakub Hrozek wrote:
> On Mon, Jul 23, 2018 at 11:08:54AM -0400,
>
On Mon, Jul 23, 2018 at 11:08:54AM -0400, sssdusers.20.retin...@spamgourmet.com
wrote:
> Unfortunately it seems to not be so easy:
> rtadmin@ubt18-test:~$ cat /etc/nsswitch.conf
> ...
> #passwd: compat systemd sss
> #group: compat systemd sss
> passwd: files sss
> group:
Unfortunately it seems to not be so easy:
rtadmin@ubt18-test:~$ cat /etc/nsswitch.conf
...
#passwd: compat systemd sss
#group: compat systemd sss
passwd: files sss
group: files sss
shadow: files sss
gshadow:files
...
rtadmin@ubt18-test:~$ getent
för Android
>
>
> From: jsl6uy js16uy
> Sent: Friday, July 20, 2018 6:49:35 PM
> To: End-user discussions about the System Security Services Daemon
> Subject: [SSSD-users] Re: "groups: cannot find name for group ID #"
>
&g
d-user discussions about the System Security Services Daemon
Subject: [SSSD-users] Re: "groups: cannot find name for group ID #"
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
i
Really? no attitude pure question. We see the same thing. These are AD
groups sssd is complaining about. We use 1.16.1 on Ubu and Centos and
see the same behavior
You're saying below should be files vs compat?
passwd: compat sss
group: compat sss
Don't get me wrong, thanks for
Start with replacing compat with files in nsswitch.conf
From: sssdusers.20.retin...@spamgourmet.com
Sent: Friday, July 20, 2018 21:47
To: sssd-users@lists.fedorahosted.org
Subject: [SSSD-users] "groups: cannot find name for group ID #"
CAUTION: This email
