-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/05/2010 07:10 AM, Sumit Bose wrote:
On Wed, Feb 03, 2010 at 09:39:20AM -0500, Stephen Gallagher wrote:
On 02/03/2010 08:30 AM, Stephen Gallagher wrote:
That said, I'm self-nacking this patch as it is written, since it seems
to be causing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/03/2010 08:08 AM, Sumit Bose wrote:
On Tue, Feb 02, 2010 at 02:14:00PM -0500, Stephen Gallagher wrote:
New patch attached.
It is now possible to specify --debug-timestamps=0 to disable them.
Now just '--debug-timestamps' does not work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/03/2010 08:30 AM, Stephen Gallagher wrote:
That said, I'm self-nacking this patch as it is written, since it seems
to be causing some trouble in the krb5_child.
Found it. I missed updating prepare_child_argv().
New patch attached.
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We will use timestamps unless they are explicitly disabled in the sssd.conf.
I am not removing the --debug_timestamps option to the services so as to
maintain backwards compatibility.
This patch resolves https://fedorahosted.org/sssd/ticket/389
- --
On Tue, 02 Feb 2010 09:50:44 -0500
Stephen Gallagher sgall...@redhat.com wrote:
We will use timestamps unless they are explicitly disabled in the
sssd.conf.
I am not removing the --debug_timestamps option to the services so as
to maintain backwards compatibility.
This patch resolves
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/2010 10:46 AM, Simo Sorce wrote:
On Tue, 02 Feb 2010 09:50:44 -0500
Stephen Gallagher sgall...@redhat.com wrote:
We will use timestamps unless they are explicitly disabled in the
sssd.conf.
I am not removing the --debug_timestamps
