Hi,
I just updated the wiki pages. I removed some duplicated
and outdated info. I hope that the pages are now clearer.
Petr
PS: If you need more info, see thread "[SSSD] [WIKI] Contribute and
DevelTips are duplicate".
___
sssd-devel mailing list
On Thu, Sep 03, 2015 at 01:50:35PM +0200, Petr Cech wrote:
> On 09/03/2015 10:08 AM, Sumit Bose wrote:
> >On Thu, Sep 03, 2015 at 09:54:51AM +0200, Jakub Hrozek wrote:
> >>On Thu, Sep 03, 2015 at 09:31:07AM +0200, Petr Cech wrote:
> >>>On 09/03/2015 08:18 AM, Jakub Hrozek wrote:
> On Thu, Sep
On 09/02/2015 05:47 PM, Jakub Hrozek wrote:
On Wed, Sep 02, 2015 at 05:18:24PM +0200, Michal Židek wrote:
On 08/17/2015 02:21 PM, Petr Cech wrote:
On 07/17/2015 01:26 PM, Petr Cech wrote:
Hi,
I have read the wiki pages. And I have the edited version. It would be
difficult to send the diff,
On Thu, Sep 03, 2015 at 06:24:35AM +0200, Lukas Slebodnik wrote:
> On (19/08/15 18:15), Jakub Hrozek wrote:
> >On Tue, Aug 18, 2015 at 05:31:43PM +0200, Michal Židek wrote:
> >> On 08/17/2015 10:35 PM, Jakub Hrozek wrote:
> >> >Hi,
> >> >
> >> >the attached patch was confirmed to work, so the code
On Wed, Sep 02, 2015 at 06:08:51PM +0200, Michal Židek wrote:
> On 09/02/2015 05:47 PM, Jakub Hrozek wrote:
> >On Wed, Sep 02, 2015 at 05:18:24PM +0200, Michal Židek wrote:
> >>On 08/17/2015 02:21 PM, Petr Cech wrote:
> >>>On 07/17/2015 01:26 PM, Petr Cech wrote:
> Hi,
>
> I have read
On Thu, Sep 03, 2015 at 06:15:24AM +0200, Lukas Slebodnik wrote:
> On (02/09/15 18:06), Petr Cech wrote:
> >Hi,
> >
> >reverting this commit "5e9bc89b28f1ac3ce573ecdece74fe9623580c28" fixed the
> >problem for me. So is the original commit no longer valid?
> >
> I'm little bit worried about
On Tue, Sep 01, 2015 at 03:21:28PM -0400, Pavel Reichl wrote:
> CI passed: http://sssd-ci.duckdns.org/logs/job/24/24/summary.html
>
> ACK to all patches.
* master:
* 3b1aa479b377e570c6dff359a1f8099289a2af75
* b0d6d14b5bcc137074383abcd2bf8039c3d74b02
*
On Thu, Sep 03, 2015 at 09:54:51AM +0200, Jakub Hrozek wrote:
> On Thu, Sep 03, 2015 at 09:31:07AM +0200, Petr Cech wrote:
> > On 09/03/2015 08:18 AM, Jakub Hrozek wrote:
> > >On Thu, Sep 03, 2015 at 06:15:24AM +0200, Lukas Slebodnik wrote:
> > >>On (02/09/15 18:06), Petr Cech wrote:
> > >>>Hi,
>
On Wed, Sep 02, 2015 at 06:21:41AM +0200, Lukas Slebodnik wrote:
> On (01/09/15 18:18), Robbie Harwood wrote:
> >This change brings the upstream packaging closer to the downstream
> >(fedora) packaging. For more information, please see
> >https://fedorahosted.org/sssd/ticket/2770
>
> >From
On (03/09/15 09:35), Jakub Hrozek wrote:
>On Wed, Sep 02, 2015 at 02:52:42PM +0200, Lukas Slebodnik wrote:
>> On (01/09/15 12:55), Michal Židek wrote:
>> >On 09/01/2015 11:11 AM, Jakub Hrozek wrote:
>> >>On Tue, Sep 01, 2015 at 11:00:15AM +0200, Lukas Slebodnik wrote:
>> >>>On (01/09/15 10:51),
On Thu, Sep 03, 2015 at 09:54:51AM +0200, Jakub Hrozek wrote:
> On Thu, Sep 03, 2015 at 09:31:07AM +0200, Petr Cech wrote:
> > On 09/03/2015 08:18 AM, Jakub Hrozek wrote:
> > >On Thu, Sep 03, 2015 at 06:15:24AM +0200, Lukas Slebodnik wrote:
> > >>On (02/09/15 18:06), Petr Cech wrote:
> > >>>Hi,
>
Hello,
please see simple patch attached.
Thanks!
>From 1dd2599ccdef13adb4d8f7a70c62e2a96942127e Mon Sep 17 00:00:00 2001
From: Pavel Reichl
Date: Thu, 3 Sep 2015 04:46:50 -0400
Subject: [PATCH] GPO: fix memory leak
Resolves:
https://fedorahosted.org/sssd/ticket/2777
---
On 09/03/2015 08:18 AM, Jakub Hrozek wrote:
On Thu, Sep 03, 2015 at 06:15:24AM +0200, Lukas Slebodnik wrote:
On (02/09/15 18:06), Petr Cech wrote:
Hi,
reverting this commit "5e9bc89b28f1ac3ce573ecdece74fe9623580c28" fixed the
problem for me. So is the original commit no longer valid?
I'm
On Wed, Sep 02, 2015 at 06:23:09AM +0200, Lukas Slebodnik wrote:
> On (01/09/15 18:19), Robbie Harwood wrote:
> >The sorted file processing is a useful guarantee to have, and is
> >provided by the current code. https://fedorahosted.org/sssd/ticket/2771
>
> >From
On Wed, Sep 02, 2015 at 02:52:42PM +0200, Lukas Slebodnik wrote:
> On (01/09/15 12:55), Michal Židek wrote:
> >On 09/01/2015 11:11 AM, Jakub Hrozek wrote:
> >>On Tue, Sep 01, 2015 at 11:00:15AM +0200, Lukas Slebodnik wrote:
> >>>On (01/09/15 10:51), Jakub Hrozek wrote:
> On Tue, Aug 11, 2015
On Wed, Sep 02, 2015 at 03:48:27PM +0200, Pavel Reichl wrote:
> On 09/02/2015 02:25 PM, Jakub Hrozek wrote:
> >On Wed, Sep 02, 2015 at 01:52:42PM +0200, Lukas Slebodnik wrote:
> >>On (02/09/15 14:39), Nikolai Kondrashov wrote:
> >>>I haven't tested it, otherwise ACK.
> >>>
> >>Thank you for
On Thu, Sep 03, 2015 at 09:31:07AM +0200, Petr Cech wrote:
> On 09/03/2015 08:18 AM, Jakub Hrozek wrote:
> >On Thu, Sep 03, 2015 at 06:15:24AM +0200, Lukas Slebodnik wrote:
> >>On (02/09/15 18:06), Petr Cech wrote:
> >>>Hi,
> >>>
> >>>reverting this commit
Hi,
due to recent memory leak issues, I think it would be good to provide a
built-in way to store talloc full report in a file. It proved to be very
helpful in detection of the location where memory leak occurs, but we
always obtained it from custom built.
I would very much like to write a
On 09/03/2015 12:56 PM, Jakub Hrozek wrote:
On Thu, Sep 03, 2015 at 12:48:20PM +0200, Pavel Březina wrote:
Hi,
due to recent memory leak issues, I think it would be good to provide a
built-in way to store talloc full report in a file. It proved to be very
helpful in detection of the location
On 09/03/2015 10:53 AM, Jakub Hrozek wrote:
On Wed, Sep 02, 2015 at 03:48:27PM +0200, Pavel Reichl wrote:
On 09/02/2015 02:25 PM, Jakub Hrozek wrote:
On Wed, Sep 02, 2015 at 01:52:42PM +0200, Lukas Slebodnik wrote:
On (02/09/15 14:39), Nikolai Kondrashov wrote:
I haven't tested it, otherwise
On 09/03/2015 12:48 PM, Pavel Březina wrote:
Hi,
due to recent memory leak issues, I think it would be good to provide a
built-in way to store talloc full report in a file. It proved to be very
helpful in detection of the location where memory leak occurs, but we always
obtained it from
On 09/03/2015 01:04 PM, Pavel Reichl wrote:
On 09/03/2015 12:48 PM, Pavel Březina wrote:
Hi,
due to recent memory leak issues, I think it would be good to provide
a built-in way to store talloc full report in a file. It proved to be
very helpful in detection of the location where memory leak
On 09/03/2015 10:08 AM, Sumit Bose wrote:
On Thu, Sep 03, 2015 at 09:54:51AM +0200, Jakub Hrozek wrote:
On Thu, Sep 03, 2015 at 09:31:07AM +0200, Petr Cech wrote:
On 09/03/2015 08:18 AM, Jakub Hrozek wrote:
On Thu, Sep 03, 2015 at 06:15:24AM +0200, Lukas Slebodnik wrote:
On (02/09/15 18:06),
On Thu, Sep 03, 2015 at 12:56:38PM +0200, Jakub Hrozek wrote:
> On Thu, Sep 03, 2015 at 12:48:20PM +0200, Pavel Březina wrote:
> > Hi,
> > due to recent memory leak issues, I think it would be good to provide a
> > built-in way to store talloc full report in a file. It proved to be very
> >
On 09/03/2015 01:11 PM, Pavel Březina wrote:
On 09/03/2015 01:04 PM, Pavel Reichl wrote:
On 09/03/2015 12:48 PM, Pavel Březina wrote:
Hi,
due to recent memory leak issues, I think it would be good to provide
a built-in way to store talloc full report in a file. It proved to be
very helpful
On Thu, Sep 03, 2015 at 01:25:33PM +0200, Sumit Bose wrote:
> Later on when some general sssctl tool is available we can add a manual
> trigger as well.
I like this idea. btw the first incarnation of this tool should come to
1.14..
___
sssd-devel
On 09/03/2015 09:58 AM, Lukas Slebodnik wrote:
On (03/09/15 09:35), Jakub Hrozek wrote:
On Wed, Sep 02, 2015 at 02:52:42PM +0200, Lukas Slebodnik wrote:
On (01/09/15 12:55), Michal Židek wrote:
On 09/01/2015 11:11 AM, Jakub Hrozek wrote:
On Tue, Sep 01, 2015 at 11:00:15AM +0200, Lukas
27 matches
Mail list logo