,
Victor
>From e485589eaec0ca5c3c866fc70fb28dd0a1e7ace6 Mon Sep 17 00:00:00 2001
From: Victor Tapia <victor.ta...@canonical.com>
Date: Fri, 12 Aug 2016 11:33:57 +0200
Subject: [PATCH] Create pidfile after responders have started
---
src/monitor/monitor.c
Hi Lukas,
> I tried to look into systemd documentation and I could not see
> anything in documentation which would say that it is a reliable
> way to use a pid file. (It might change in future if it is not documented)
>
> man systemd.service says
>If set to forking, it is expected
>>
>> I haven't tried using "Type=notify", but I don't think it would make a
>> difference if we can't hold the notification signal until the responders
>> are running.
>>
> You would need to call sd_*notify function after initialisation of responders
> man 3 sd_notify
>
ation or
>dyndns updates?
In this case, the retry after a failure connecting to an LDAP server
Kind regards,
Victor
On Thu, Feb 9, 2017 at 9:37 PM, Jakub Hrozek <jhro...@redhat.com> wrote:
> On Thu, Feb 09, 2017 at 05:55:57PM +0100, Victor Tapia wrote:
> > Hi list,
> >
&g
El 10/02/17 a las 09:28, Jakub Hrozek escribió:
> On Thu, Feb 09, 2017 at 09:50:18PM +0100, Victor Tapia wrote:
>>>> I've been testing a scenario with a time shift of an hour to the past,
>>>> and even though the watchdog detects the shift and restarts, the
>>&g
Hi list,
I've been testing a scenario with a time shift of an hour to the past,
and even though the watchdog detects the shift and restarts, the
scheduled events are still stuck until the time passes.
Would it make sense to use the same resetOffline/SIGUSR2 mechanism used
for networking status
El 01/09/16 a las 14:50, Lukas Slebodnik escribió:
> On (26/08/16 13:16), Victor Tapia wrote:
>> Hi,
>>
>> Sorry for the late response, I've been out for nearly two weeks. I'm
>> attaching a new version of the patch to review.
>>
>>> Does upstart/init scri
El 08/09/16 a las 13:13, Lukas Slebodnik escribió:
> On (08/09/16 12:29), Victor Tapia wrote:
>> El 01/09/16 a las 14:50, Lukas Slebodnik escribió:
>>> On (26/08/16 13:16), Victor Tapia wrote:
>>>> Hi,
>>>>
>>>> Sorry for the late response,
El 03/10/16 a las 21:34, Jakub Hrozek escribió:
> On Mon, Oct 03, 2016 at 05:44:19PM +0200, Victor Tapia wrote:
>> Hi,
>>
>> I just removed the upstart part and left just the systemd notification
>> with the fix for the latest master branch. I also fixed the evalu
Hi,
I just saw that the ticket 3080 (https://fedorahosted.org/sssd/ticket/3080) has
been closed with a different patch. Is this one landing too?
Thanks,
Victor
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an
tify for systemd.
Thanks,
Victor
>From 65f587535fae28719d3f2455fe144dd008361d52 Mon Sep 17 00:00:00 2001
From: Victor Tapia <victor.ta...@canonical.com>
Date: Fri, 26 Aug 2016 13:01:32 +0200
Subject: [PATCH] Create pidfile after responders started
---
Makefile.am |
kub Hrozek escribió:
> On Thu, Sep 22, 2016 at 10:07:21AM -, Victor Tapia wrote:
>> Hi,
>>
>> I just saw that the ticket 3080 (https://fedorahosted.org/sssd/ticket/3080)
>> has been closed with a different patch. Is this one landing too?
>
> Sorry, that
Hi Lukas,
please let me know if you need anything else for this patch.
Regards,
Victor
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
Hi Lukas,
could you review this patch and let me if it's ok as it is?
Thanks,
Victor
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
Hi, I was out last week, sorry for the delay!
The patch looks good to me, I'll try to test it too as soon as I find some time.
Thanks,
Victor
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to
Hi Fabiano and list,
Please forgive me, I just realized that I wasn't, indeed, running from
master. I'll try again with the proper version and come back if needed.
Thanks!
Victor
El 10/10/16 a las 10:09, Fabiano Fidêncio escribió:
> Victor,
>
> On Mon, Oct 10, 2016 at 10:04 AM, Vic
Hi list,
I've faced a race condition when SSSD boots in a machine with a big
clock drift. This is what I see:
1. SSSD starts before the network is up, queries the LDAP server without
success and sets a retry timer (~60 secs)
2. NTP starts and corrects the clock, 1 hour back for example.
3. SSSD
El 10/10/16 a las 10:56, Ian Kent escribió:
> On Mon, 2016-10-10 at 10:42 +0200, Jakub Hrozek wrote:
>> On Mon, Oct 10, 2016 at 10:04:30AM +0200, Victor Tapia wrote:
>>> Hi list,
>>>
>>> I've faced a race condition when SSSD boots in a machine with a big
Hi Lukas,
Just wanted to confirm your patch works for me.
Kind regards,
Victor
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
19 matches
Mail list logo
