On Wed, Aug 15, 2012 at 12:36:31PM -0400, Dmitri Pal wrote:
On 08/15/2012 11:31 AM, Jakub Hrozek wrote:
> On Wed, Aug 15, 2012 at 11:16:10AM -0400, Dmitri Pal wrote:
>>> *adinfo* - tell the user is there is some working connection to any
>>> ldap server or whether we are running completely in the disconnected
>>> mode. Right now I have to dig through the logs to find out.
>>> I think both have been discussed here, but the idea was eventually
>>> abandoned by the sssd developers
>> Yes I agree having a way to dump current status of the SSSD responders
>> and providers would be a nice to have. But it is not quite simple.
>> I think we have a ticket for this.
>> See some thoughts that Stephen recorded there:
>>
https://fedorahosted.org/sssd/ticket/385#comment:12
>>
> Would something as simple as logging changes to online/offline status to
> syslog with a lower severity (LOG_INFO or LOG_DEBUG) be useful?
>
> Recent systemd versions also print the last couple of lines that the
> service logged when "service foo status" (aka systemctl status
> foo.service) is called.
>
> Then calling "service sssd status" would be able to tell you the last
> status change of the provider.
Do you plan to issue a message per provider per domain?
In this case you might end up with multiple messages.
Yes, I was thinking a message per provider. That might get verbose in a
multi-domain environment, but I don't suspect there would be many setups
with many domains, even in an AD-trust setup.
Can status command support arguments like:
service sssd status --domain=ipa --provider=id
or
service sssd status --domain=ad --provider=pwd_change
Then we can have one message per domain per provider.
service is just a wrapper around systemctl from systemd, we don't control it.