Comment 3 for bug 1880157

This is not a fatal error, as the non-socket-activated instances of the service startup. It's incorrect though, as the sssd package defaults to socket-activated and realmd should be in sync with that.

Example right after joining the domain:
    579 ? Ss 0:00 /usr/sbin/sssd -i --logger=files
    580 ? S 0:00 \_ /usr/libexec/sssd/sssd_be --domain ad1.example.com --uid 0 --gid 0 --logger=files
    581 ? S 0:00 \_ /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files
    582 ? S 0:00 \_ /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --logger=files
    618 ? Ss 0:00 /usr/libexec/sssd/sssd_sudo --socket-activated

We see that nss and pam started in their non-socket-activated modes, because they are specified in sssd.conf, whereas sudo, which is NOT specified in sssd.conf, started as socket-activated.

I'm downgrading the severity, but it's still worth fixing.