On 09/29/2015 07:53 PM, Jakub Hrozek wrote:
On Tue, Sep 29, 2015 at 06:15:35PM +0200, Sumit Bose wrote:
On Tue, Sep 29, 2015 at 05:57:32PM +0200, Jakub Hrozek wrote:
On Mon, Sep 28, 2015 at 10:18:07AM +0200, Sumit Bose wrote:
On Mon, Jun 29, 2015 at 11:07:30PM -0400, Dan Lavu wrote:
I've
On 10/01/2015 09:58 AM, Pavel Březina wrote:
On 09/29/2015 07:53 PM, Jakub Hrozek wrote:
On Tue, Sep 29, 2015 at 06:15:35PM +0200, Sumit Bose wrote:
On Tue, Sep 29, 2015 at 05:57:32PM +0200, Jakub Hrozek wrote:
On Mon, Sep 28, 2015 at 10:18:07AM +0200, Sumit Bose wrote:
On Mon, Jun 29,
On Tue, Sep 29, 2015 at 07:53:41PM +0200, Jakub Hrozek wrote:
> On Tue, Sep 29, 2015 at 06:15:35PM +0200, Sumit Bose wrote:
> > On Tue, Sep 29, 2015 at 05:57:32PM +0200, Jakub Hrozek wrote:
> > > On Mon, Sep 28, 2015 at 10:18:07AM +0200, Sumit Bose wrote:
> > > > On Mon, Jun 29, 2015 at 11:07:30PM
On Wed, Sep 30, 2015 at 01:10:20PM +0200, Petr Cech wrote:
> On 09/30/2015 11:15 AM, Jakub Hrozek wrote:
> >On Wed, Sep 30, 2015 at 09:53:24AM +0200, Sumit Bose wrote:
> >>It's https://fedorahosted.org/sssd/ticket/2808 . Please add ideas and
> >>suggestions how those tags shall look like.
> >
>
On Wed, Sep 30, 2015 at 09:53:24AM +0200, Sumit Bose wrote:
> It's https://fedorahosted.org/sssd/ticket/2808 . Please add ideas and
> suggestions how those tags shall look like.
Thanks, I ressurected
https://fedorahosted.org/sssd/ticket/1372 from Deferred as well.
On 09/30/2015 11:15 AM, Jakub Hrozek wrote:
On Wed, Sep 30, 2015 at 09:53:24AM +0200, Sumit Bose wrote:
It's https://fedorahosted.org/sssd/ticket/2808 . Please add ideas and
suggestions how those tags shall look like.
Thanks, I ressurected
https://fedorahosted.org/sssd/ticket/1372 from
On Mon, Sep 28, 2015 at 10:18:07AM +0200, Sumit Bose wrote:
> On Mon, Jun 29, 2015 at 11:07:30PM -0400, Dan Lavu wrote:
> > I've been watching various logs for the past few minutes, FWIW, I think a
> > more casual message will help people better understand what SSSD is doing.
> > Look at debug
On Tue, Sep 29, 2015 at 05:57:32PM +0200, Jakub Hrozek wrote:
> On Mon, Sep 28, 2015 at 10:18:07AM +0200, Sumit Bose wrote:
> > On Mon, Jun 29, 2015 at 11:07:30PM -0400, Dan Lavu wrote:
> > > I've been watching various logs for the past few minutes, FWIW, I think a
> > > more casual message will
On Tue, Sep 29, 2015 at 06:15:35PM +0200, Sumit Bose wrote:
> On Tue, Sep 29, 2015 at 05:57:32PM +0200, Jakub Hrozek wrote:
> > On Mon, Sep 28, 2015 at 10:18:07AM +0200, Sumit Bose wrote:
> > > On Mon, Jun 29, 2015 at 11:07:30PM -0400, Dan Lavu wrote:
> > > > I've been watching various logs for
On 09/29/2015 07:53 PM, Jakub Hrozek wrote:
On Tue, Sep 29, 2015 at 06:15:35PM +0200, Sumit Bose wrote:
On Tue, Sep 29, 2015 at 05:57:32PM +0200, Jakub Hrozek wrote:
On Mon, Sep 28, 2015 at 10:18:07AM +0200, Sumit Bose wrote:
On Mon, Jun 29, 2015 at 11:07:30PM -0400, Dan Lavu wrote:
I've
ity Services Daemon"
> > <sssd-devel@lists.fedorahosted.org>
> > Cc: "George Agriogiannis" <gagri...@redhat.com>, "Dan Lavu"
> > <dl...@redhat.com>
> > Sent: Monday, June 29, 2015 5:53:45 PM
> > Subject: Re: [SSSD] RFC: Improving
On Mon, Jul 13, 2015 at 09:34:23AM +0200, Lukas Slebodnik wrote:
On (01/07/15 12:48), Jakub Hrozek wrote:
On Wed, Jul 01, 2015 at 12:03:48PM +0200, Pavel Březina wrote:
On 06/29/2015 06:13 PM, Jakub Hrozek wrote:
Hi,
I spent many hours debugging SSSD in different scenarios last week and
On (01/07/15 10:03), Jakub Hrozek wrote:
On Tue, Jun 30, 2015 at 11:28:39PM +0200, Lukas Slebodnik wrote:
- Running sssd in environment where all actions complete successfully
should emit no debug messages. Default log level should be moved to
SSSDBG_OP_FAILURE or CRIT_FAILURE. (This
On (01/07/15 12:48), Jakub Hrozek wrote:
On Wed, Jul 01, 2015 at 12:03:48PM +0200, Pavel Březina wrote:
On 06/29/2015 06:13 PM, Jakub Hrozek wrote:
Hi,
I spent many hours debugging SSSD in different scenarios last week and I
admit it wasn't always easy -- and I have the source code knowledge
On 06/29/2015 06:13 PM, Jakub Hrozek wrote:
Hi,
I spent many hours debugging SSSD in different scenarios last week and I
admit it wasn't always easy -- and I have the source code knowledge I
can use. I imagine it's considerably harder for users and admins..
So this is a brainstorm request on
On 07/01/2015 12:48 PM, Jakub Hrozek wrote:
On Wed, Jul 01, 2015 at 12:03:48PM +0200, Pavel Březina wrote:
On 06/29/2015 06:13 PM, Jakub Hrozek wrote:
Hi,
I spent many hours debugging SSSD in different scenarios last week and I
admit it wasn't always easy -- and I have the source code
On Wed, Jul 01, 2015 at 12:03:48PM +0200, Pavel Březina wrote:
On 06/29/2015 06:13 PM, Jakub Hrozek wrote:
Hi,
I spent many hours debugging SSSD in different scenarios last week and I
admit it wasn't always easy -- and I have the source code knowledge I
can use. I imagine it's considerably
On Tue, Jun 30, 2015 at 11:28:39PM +0200, Lukas Slebodnik wrote:
- Running sssd in environment where all actions complete successfully
should emit no debug messages. Default log level should be moved to
SSSDBG_OP_FAILURE or CRIT_FAILURE. (This basically amounts to checking
all OP, FATAL
On Mon, Jun 29, 2015 at 06:13:20PM +0200, Jakub Hrozek wrote:
So this is a brainstorm request on how can we make debugging with SSSD
easier. Maybe there are some low-hanging fruits that can be fixed
easily. Off the top of my head:
- it should be easier to see start and end of a request in
On Tue, 2015-06-30 at 12:04 +0200, Jakub Hrozek wrote:
On Tue, Jun 30, 2015 at 10:30:16AM +0200, Jan Pazdziora wrote:
- Running sssd in environment where all actions complete
successfully
should emit no debug messages. Default log level should be
moved to
SSSDBG_OP_FAILURE or
On Tue, Jun 30, 2015 at 07:58:45AM -0400, Stephen Gallagher wrote:
On Tue, 2015-06-30 at 12:04 +0200, Jakub Hrozek wrote:
On Tue, Jun 30, 2015 at 10:30:16AM +0200, Jan Pazdziora wrote:
- Running sssd in environment where all actions complete
successfully
should emit no debug
On Tue, Jun 30, 2015 at 10:30:16AM +0200, Jan Pazdziora wrote:
- Running sssd in environment where all actions complete successfully
should emit no debug messages. Default log level should be moved to
SSSDBG_OP_FAILURE or CRIT_FAILURE. (This basically amounts to checking
all OP,
On (29/06/15 18:13), Jakub Hrozek wrote:
Hi,
I spent many hours debugging SSSD in different scenarios last week and I
admit it wasn't always easy -- and I have the source code knowledge I
can use. I imagine it's considerably harder for users and admins..
So this is a brainstorm request on how
Hi,
I spent many hours debugging SSSD in different scenarios last week and I
admit it wasn't always easy -- and I have the source code knowledge I
can use. I imagine it's considerably harder for users and admins..
So this is a brainstorm request on how can we make debugging with SSSD
easier.
On Mon, 2015-06-29 at 18:13 +0200, Jakub Hrozek wrote:
Hi,
I spent many hours debugging SSSD in different scenarios last week and I
admit it wasn't always easy -- and I have the source code knowledge I
can use. I imagine it's considerably harder for users and admins..
So this is a
: Improving the debug messages
On Mon, 2015-06-29 at 18:13 +0200, Jakub Hrozek wrote:
Hi,
I spent many hours debugging SSSD in different scenarios last week
and I
admit it wasn't always easy -- and I have the source code knowledge
I
can use. I imagine it's considerably harder for users
26 matches
Mail list logo
