[SSSD] [sssd PR#144][comment] SSSD does not start if using only the local provider and services line is empty

2017-02-09 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/144 Title: #144: SSSD does not start if using only the local provider and services line is empty jhrozek commented: """ I think we need to decide how we solve the local provider auto-enablement. Currently my idea (which is not in the current files provide

[SSSD] [sssd PR#144][comment] SSSD does not start if using only the local provider and services line is empty

2017-02-09 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/144 Title: #144: SSSD does not start if using only the local provider and services line is empty jhrozek commented: """ I think we need to decide how we solve the local provider auto-enablement. Currently my idea (which is not in the current files provide

[SSSD] [sssd PR#144][comment] SSSD does not start if using only the local provider and services line is empty

2017-02-09 Thread simo5
URL: https://github.com/SSSD/sssd/pull/144 Title: #144: SSSD does not start if using only the local provider and services line is empty simo5 commented: """ FWIW, I do not see any risk in pushing this patch as it is, and adjusting the code in the files PR if it changes anything. """ See the f

[SSSD] [sssd PR#146][comment] Avoid running two instances of the same service

2017-02-09 Thread pbrezina
URL: https://github.com/SSSD/sssd/pull/146 Title: #146: Avoid running two instances of the same service pbrezina commented: """ My opinion is do not use sync code when use can use async. """ See the full comment at https://github.com/SSSD/sssd/pull/146#issuecomment-278597300 __

[SSSD] [sssd PR#152][opened] Add a tevent wrapper around libcurl's asynchronous interface

2017-02-09 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/152 Author: jhrozek Title: #152: Add a tevent wrapper around libcurl's asynchronous interface Action: opened PR body: """ This patch set adds a generic utility module that uses libcurl's multi interface to allow the caller to talk HTTP using libcurl. The

[SSSD] [sssd PR#137][synchronized] Initial pkinit support

2017-02-09 Thread sumit-bose
URL: https://github.com/SSSD/sssd/pull/137 Author: sumit-bose Title: #137: Initial pkinit support Action: synchronized To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/137/head:pr137 git checkout pr137 From f00c519abdd485e2c310661c2df21b055

[SSSD] [sssd PR#137][comment] Initial pkinit support

2017-02-09 Thread sumit-bose
URL: https://github.com/SSSD/sssd/pull/137 Title: #137: Initial pkinit support sumit-bose commented: """ Thank you for running the tests, the valgirind issue was the same as the last coverity warning. """ See the full comment at https://github.com/SSSD/sssd/pull/137#issuecomment-278608541 ___

[SSSD] [sssd PR#152][comment] Add a tevent wrapper around libcurl's asynchronous interface

2017-02-09 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/152 Title: #152: Add a tevent wrapper around libcurl's asynchronous interface jhrozek commented: """ I changed three patches a bit: * the build patch now detects if libcurl supports unix sockets and skips building the curl code if not completely. Pavel, y

[SSSD] [sssd PR#152][synchronized] Add a tevent wrapper around libcurl's asynchronous interface

2017-02-09 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/152 Author: jhrozek Title: #152: Add a tevent wrapper around libcurl's asynchronous interface Action: synchronized To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/152/head:pr152 git checkout pr152 Fro

[SSSD] [sssd PR#145][+Accepted] Fix storing a sudoRule attriubute in a case-insensitive domain when the attriubute values differ only by case

2017-02-09 Thread fidencio
URL: https://github.com/SSSD/sssd/pull/145 Title: #145: Fix storing a sudoRule attriubute in a case-insensitive domain when the attriubute values differ only by case Label: +Accepted ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To

[SSSD] Watchdog, time shifts and scheduled events

2017-02-09 Thread Victor Tapia
Hi list, I've been testing a scenario with a time shift of an hour to the past, and even though the watchdog detects the shift and restarts, the scheduled events are still stuck until the time passes. Would it make sense to use the same resetOffline/SIGUSR2 mechanism used for networking status ch

[SSSD] Re: Watchdog, time shifts and scheduled events

2017-02-09 Thread Jakub Hrozek
On Thu, Feb 09, 2017 at 05:55:57PM +0100, Victor Tapia wrote: > Hi list, > > I've been testing a scenario with a time shift of an hour to the past, > and even though the watchdog detects the shift and restarts, the > scheduled events are still stuck until the time passes. What kind of scheduled e

[SSSD] Re: Watchdog, time shifts and scheduled events

2017-02-09 Thread Victor Tapia
>> I've been testing a scenario with a time shift of an hour to the past, >> and even though the watchdog detects the shift and restarts, the >> scheduled events are still stuck until the time passes. > >What kind of scheduled events? The periodical tasks like enumeration or >dyndns updates? In th