On Thu, Jun 27, 2013 at 01:04:48PM +0200, Lukas Slebodnik wrote:
> On (27/06/13 10:20), Pavel Březina wrote:
> >On 06/26/2013 05:32 PM, Lukas Slebodnik wrote:
> >>On (26/06/13 10:49), Pavel Březina wrote:
> >>>https://fedorahosted.org/sssd/ticket/1693
> >>>
> >>>The reason why sudo show different m
On (27/06/13 10:20), Pavel Březina wrote:
>On 06/26/2013 05:32 PM, Lukas Slebodnik wrote:
>>On (26/06/13 10:49), Pavel Březina wrote:
>>>https://fedorahosted.org/sssd/ticket/1693
>>>
>>>The reason why sudo show different messages is that SSSD crashes
>>>(SIGABRT from talloc) when out of band refres
On 06/26/2013 05:32 PM, Lukas Slebodnik wrote:
On (26/06/13 10:49), Pavel Březina wrote:
https://fedorahosted.org/sssd/ticket/1693
The reason why sudo show different messages is that SSSD crashes
(SIGABRT from talloc) when out of band refresh is finished. For some
reason, Nikolai's test is much
On (26/06/13 10:49), Pavel Březina wrote:
>https://fedorahosted.org/sssd/ticket/1693
>
>The reason why sudo show different messages is that SSSD crashes
>(SIGABRT from talloc) when out of band refresh is finished. For some
>reason, Nikolai's test is much more likely to reveal this on rhel
>systems
On 06/26/2013 10:49 AM, Pavel Březina wrote:
https://fedorahosted.org/sssd/ticket/1693
The reason why sudo show different messages is that SSSD crashes
(SIGABRT from talloc) when out of band refresh is finished. For some
reason, Nikolai's test is much more likely to reveal this on rhel
systems t
https://fedorahosted.org/sssd/ticket/1693
The reason why sudo show different messages is that SSSD crashes
(SIGABRT from talloc) when out of band refresh is finished. For some
reason, Nikolai's test is much more likely to reveal this on rhel
systems than on fedora, however the SSSD crashes on
