On Tue, Jun 13, 2017 at 06:21:28PM +, Joakim Tjernlund wrote:
> On Tue, 2017-06-13 at 18:01 +0200, Jakub Hrozek wrote:
> > On Tue, Jun 13, 2017 at 12:12:05PM +, Joakim Tjernlund wrote:
> > > > It is now :) was in the wrong section before
> > >
> > > timeout = 30 in domain section SEEMS to
On Tue, Jun 13, 2017 at 06:18:24PM +, Joakim Tjernlund wrote:
> On Tue, 2017-06-13 at 17:59 +0200, Jakub Hrozek wrote:
> > On Tue, Jun 13, 2017 at 12:34:41PM +, Joakim Tjernlund wrote:
> > > > timeout = 30 in domain section SEEMS to help, no problem since
> > > > yesterday.
> > > > What di
On Tue, 2017-06-13 at 18:01 +0200, Jakub Hrozek wrote:
> On Tue, Jun 13, 2017 at 12:12:05PM +, Joakim Tjernlund wrote:
> > > It is now :) was in the wrong section before
> >
> > timeout = 30 in domain section SEEMS to help, no problem since yesterday.
> > What did I really do here?
>
> There
On Tue, 2017-06-13 at 17:59 +0200, Jakub Hrozek wrote:
> On Tue, Jun 13, 2017 at 12:34:41PM +, Joakim Tjernlund wrote:
> > > timeout = 30 in domain section SEEMS to help, no problem since yesterday.
> > > What did I really do here?
> > >
> >
> > However, now I see that getent group/getent gro
On Tue, Jun 13, 2017 at 12:12:05PM +, Joakim Tjernlund wrote:
> > It is now :) was in the wrong section before
>
> timeout = 30 in domain section SEEMS to help, no problem since yesterday.
> What did I really do here?
There is a ticket to document this better already but tl;dr there is a
watc
On Tue, Jun 13, 2017 at 12:34:41PM +, Joakim Tjernlund wrote:
> > timeout = 30 in domain section SEEMS to help, no problem since yesterday.
> > What did I really do here?
> >
>
> However, now I see that getent group/getent group is incomplete,
> members are missing.
> And it varies between
On Tue, 2017-06-13 at 14:12 +0200, Joakim Tjernlund wrote:
> On Mon, 2017-06-12 at 18:06 +0200, Joakim Tjernlund wrote:
> > On Mon, 2017-06-12 at 17:51 +0200, Jakub Hrozek wrote:
> > > On Mon, Jun 12, 2017 at 03:38:28PM +, Joakim Tjernlund wrote:
> > > > On Mon, 2017-06-12 at 17:32 +0200, Joaki
On Mon, 2017-06-12 at 18:06 +0200, Joakim Tjernlund wrote:
> On Mon, 2017-06-12 at 17:51 +0200, Jakub Hrozek wrote:
> > On Mon, Jun 12, 2017 at 03:38:28PM +, Joakim Tjernlund wrote:
> > > On Mon, 2017-06-12 at 17:32 +0200, Joakim Tjernlund wrote:
> > > > On Mon, 2017-06-12 at 16:01 +0200, Jakub
On Mon, 2017-06-12 at 17:57 +0200, Jakub Hrozek wrote:
> On Mon, Jun 12, 2017 at 03:21:43PM +, Joakim Tjernlund wrote:
> > On Mon, 2017-06-12 at 16:01 +0200, Jakub Hrozek wrote:
> > > On Mon, Jun 12, 2017 at 01:53:27PM +, Joakim Tjernlund wrote:
> > > > On Sun, 2017-06-11 at 20:55 +0200, Ja
On Mon, 2017-06-12 at 17:51 +0200, Jakub Hrozek wrote:
> On Mon, Jun 12, 2017 at 03:38:28PM +, Joakim Tjernlund wrote:
> > On Mon, 2017-06-12 at 17:32 +0200, Joakim Tjernlund wrote:
> > > On Mon, 2017-06-12 at 16:01 +0200, Jakub Hrozek wrote:
> > > > On Mon, Jun 12, 2017 at 01:53:27PM +, Jo
On Mon, Jun 12, 2017 at 03:21:43PM +, Joakim Tjernlund wrote:
> On Mon, 2017-06-12 at 16:01 +0200, Jakub Hrozek wrote:
> > On Mon, Jun 12, 2017 at 01:53:27PM +, Joakim Tjernlund wrote:
> > > On Sun, 2017-06-11 at 20:55 +0200, Jakub Hrozek wrote:
> > > > On Sat, Jun 10, 2017 at 07:56:47AM +0
On Mon, Jun 12, 2017 at 03:32:22PM +, Joakim Tjernlund wrote:
> On Mon, 2017-06-12 at 16:01 +0200, Jakub Hrozek wrote:
> > On Mon, Jun 12, 2017 at 01:53:27PM +, Joakim Tjernlund wrote:
> > > On Sun, 2017-06-11 at 20:55 +0200, Jakub Hrozek wrote:
> > > > On Sat, Jun 10, 2017 at 07:56:47AM +0
On Mon, Jun 12, 2017 at 03:38:28PM +, Joakim Tjernlund wrote:
> On Mon, 2017-06-12 at 17:32 +0200, Joakim Tjernlund wrote:
> > On Mon, 2017-06-12 at 16:01 +0200, Jakub Hrozek wrote:
> > > On Mon, Jun 12, 2017 at 01:53:27PM +, Joakim Tjernlund wrote:
> > > > On Sun, 2017-06-11 at 20:55 +0200
On Mon, 2017-06-12 at 17:32 +0200, Joakim Tjernlund wrote:
> On Mon, 2017-06-12 at 16:01 +0200, Jakub Hrozek wrote:
> > On Mon, Jun 12, 2017 at 01:53:27PM +, Joakim Tjernlund wrote:
> > > On Sun, 2017-06-11 at 20:55 +0200, Jakub Hrozek wrote:
> > > > On Sat, Jun 10, 2017 at 07:56:47AM +, Jo
On Mon, 2017-06-12 at 16:01 +0200, Jakub Hrozek wrote:
> On Mon, Jun 12, 2017 at 01:53:27PM +, Joakim Tjernlund wrote:
> > On Sun, 2017-06-11 at 20:55 +0200, Jakub Hrozek wrote:
> > > On Sat, Jun 10, 2017 at 07:56:47AM +, Joakim Tjernlund wrote:
> > > > On Sat, 2017-06-10 at 08:24 +0200, Ja
On Mon, 2017-06-12 at 16:01 +0200, Jakub Hrozek wrote:
> On Mon, Jun 12, 2017 at 01:53:27PM +, Joakim Tjernlund wrote:
> > On Sun, 2017-06-11 at 20:55 +0200, Jakub Hrozek wrote:
> > > On Sat, Jun 10, 2017 at 07:56:47AM +, Joakim Tjernlund wrote:
> > > > On Sat, 2017-06-10 at 08:24 +0200, Ja
On Mon, Jun 12, 2017 at 01:53:27PM +, Joakim Tjernlund wrote:
> On Sun, 2017-06-11 at 20:55 +0200, Jakub Hrozek wrote:
> > On Sat, Jun 10, 2017 at 07:56:47AM +, Joakim Tjernlund wrote:
> > > On Sat, 2017-06-10 at 08:24 +0200, Jakub Hrozek wrote:
> > > > On Fri, Jun 09, 2017 at 04:28:45PM +0
On Sun, 2017-06-11 at 20:55 +0200, Jakub Hrozek wrote:
> On Sat, Jun 10, 2017 at 07:56:47AM +, Joakim Tjernlund wrote:
> > On Sat, 2017-06-10 at 08:24 +0200, Jakub Hrozek wrote:
> > > On Fri, Jun 09, 2017 at 04:28:45PM +, Joakim Tjernlund wrote:
> > > > both 1.15.2 and git master hangs afte
On Mon, 12 Jun 2017, Joakim Tjernlund wrote:
hmm, isn't "offline" login creds stored here as well? Then having a RAM fs will
delete
the offline cred's each reboot. Is there a way around this?
You could sync it elsewhere on shutdown perhaps?
So far we've got away with not using tmpfs on machi
On Mon, 2017-06-12 at 10:29 +0200, Joakim Tjernlund wrote:
> On Mon, 2017-06-12 at 09:19 +0100, John Hodrien wrote:
> > On Sun, 11 Jun 2017, Jakub Hrozek wrote:
> >
> > > Oh, sure. The other alternative might be to mount the cache to tmpfs.
> >
> > I'm an advocate of this method. With older vers
On Mon, Jun 12, 2017 at 08:29:29AM +, Joakim Tjernlund wrote:
> On Mon, 2017-06-12 at 09:19 +0100, John Hodrien wrote:
> > On Sun, 11 Jun 2017, Jakub Hrozek wrote:
> >
> > > Oh, sure. The other alternative might be to mount the cache to tmpfs.
> >
> > I'm an advocate of this method. With old
On Mon, 2017-06-12 at 09:19 +0100, John Hodrien wrote:
> On Sun, 11 Jun 2017, Jakub Hrozek wrote:
>
> > Oh, sure. The other alternative might be to mount the cache to tmpfs.
>
> I'm an advocate of this method. With older versions of SSSD, against our
> relatively large AD, the performance boost
On Sun, 11 Jun 2017, Jakub Hrozek wrote:
Oh, sure. The other alternative might be to mount the cache to tmpfs.
I'm an advocate of this method. With older versions of SSSD, against our
relatively large AD, the performance boost from running with tmpfs was
immense. This advantage has been redu
On Sat, Jun 10, 2017 at 07:56:47AM +, Joakim Tjernlund wrote:
> On Sat, 2017-06-10 at 08:24 +0200, Jakub Hrozek wrote:
> > On Fri, Jun 09, 2017 at 04:28:45PM +, Joakim Tjernlund wrote:
> > > both 1.15.2 and git master hangs after less than 24 hour on
> > > a server.
> > >
> > > I can see t
On Sat, 2017-06-10 at 08:24 +0200, Jakub Hrozek wrote:
> On Fri, Jun 09, 2017 at 04:28:45PM +, Joakim Tjernlund wrote:
> > both 1.15.2 and git master hangs after less than 24 hour on
> > a server.
> >
> > I can see this repeating the domain log:
> >
> > (Fri Jun 9 18:21:49 2017) [sssd[be[inf
On Fri, Jun 09, 2017 at 04:28:45PM +, Joakim Tjernlund wrote:
> both 1.15.2 and git master hangs after less than 24 hour on
> a server.
>
> I can see this repeating the domain log:
>
> (Fri Jun 9 18:21:49 2017) [sssd[be[infinera.com]]] [orderly_shutdown]
> (0x0010): SIGTERM: killing childre
26 matches
Mail list logo