[SSSD] [sssd PR#702][comment] NSS: Avoid changing the memory cache ownership away from the SSSD user

2018-12-13 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/702 Title: #702: NSS: Avoid changing the memory cache ownership away from the SSSD user jhrozek commented: """ * master: 61e4ba58934b20a950255e05797aca25aadc1242 I'll submit a 1-16 backport separately """ See the full comment at https://github.com/SSSD/

[SSSD] [sssd PR#702][comment] NSS: Avoid changing the memory cache ownership away from the SSSD user

2018-12-12 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/702 Title: #702: NSS: Avoid changing the memory cache ownership away from the SSSD user mzidek-rh commented: """ Thanks. CI passed except for unrelated failure on debian and jhrozek showed me the fix in interactive session. ACK. """ See the full comment

[SSSD] [sssd PR#702][comment] NSS: Avoid changing the memory cache ownership away from the SSSD user

2018-12-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/702 Title: #702: NSS: Avoid changing the memory cache ownership away from the SSSD user jhrozek commented: """ OK, the comment is there. I also did some more changes, because the integration tests started failing intermittently. This was beause each inva

[SSSD] [sssd PR#702][comment] NSS: Avoid changing the memory cache ownership away from the SSSD user

2018-12-04 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/702 Title: #702: NSS: Avoid changing the memory cache ownership away from the SSSD user mzidek-rh commented: """ Could you add comment before this code (the comment can be "Make sure that the memory cache files are chowned to sssd.sssd even if the nss res

[SSSD] [sssd PR#702][comment] NSS: Avoid changing the memory cache ownership away from the SSSD user

2018-12-04 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/702 Title: #702: NSS: Avoid changing the memory cache ownership away from the SSSD user jhrozek commented: """ retest this please """ See the full comment at https://github.com/SSSD/sssd/pull/702#issuecomment-444096255 ___