On Wed, Feb 8, 2017 at 1:14 PM, Lukas Slebodnik <lslebodn(a)redhat.com> wrote:
On (08/02/17 12:33), Fabiano Fidêncio wrote:
>On Wed, Feb 8, 2017 at 12:29 PM, Lukas Slebodnik <lslebodn(a)redhat.com> wrote:
>> On (08/02/17 12:24), Fabiano Fidêncio wrote:
>>>On Wed, Feb 8, 2017 at 12:10 PM, Lukas Slebodnik <lslebodn(a)redhat.com>
wrote:
>>>> On (05/02/17 23:24), Fabiano Fidêncio wrote:
>>>>>I've spent some amount of time trying to properly deal with this
issue
>>>>>and I really need the opinion/suggestion of more experienced
>>>>>developers.
>>>>>
>>>>>Basically, as explained in #3300 this situation can happen is two
>>>>>scenarios were the admin is mixing up socket-activated and explicitly
>>>>>configured services:
>>>>>- Scenario 1:
>>>>> - nss responder is explicitly activated;
>>>>> - nss responder's socket is enabled;
>>>>> - boot the system
>>>>> - both nss processes will be up
>>>>>
>>>> This is pure misconfuguration and I do not think a reason why we shoudl
solve
>>>> it.
>>>
>>>Do you prefer to not deal with a misconfiguration scneraio (that may
>>>not be caused by the admins themselves, but by the packager ...) even
>>>if we can do that?
>>>Interesting, at least.
>>>
>> Yes, I do not want to deal with misconfiguration.
>> We might passively detect it and refuse such state.
>> e.g. Fail if unix sockets are already created(by systemd) and monitor
>> wants to start responders.
>
>How do we prevent systemd to start a responder in case the responder
>has been already started by the monitor?
>How do you cope with this "mixed" scenario?
>
Systemd sockets are created earlier in the boot phase.
They are because systemd automatically adds any socket to be started
during sockets.target start up, but they shouldn't according to our
design page.
According to the design page the sockets would be started when SSSD is started.
May be the case the design done is wrong? Of course.
So, let's get back to the design page as the first thing and solve the
problems we have there.
> So this situation will not happen at boot.
>
> And if sssd is already started I wonder how systemd can create
> sockets which are already owned by other process.
>
> LS
> _______________________________________________
> sssd-devel mailing list -- sssd-devel(a)lists.fedorahosted.org
> To unsubscribe send an email to sssd-devel-leave(a)lists.fedorahosted.org