Shibboleth SP on RHEL7- issues between shibd <-> systemd?

[Cantor, Scott]

On 6/9/15, 6:33 AM, "Jarno Huuskonen" <jarno.huuskonen at uef.fi> wrote:


>
>Ok thanks for clarifying this.
>Is InCommon/edugain metadata good example of metadata that takes a long 
>time
>to load/process (and needs long -w time) ?
>(Quick testing when I add both InCommon/Edugain metadata it takes about
>+75s from shibd start to listener->run).

InCommon probably does, but UK metadata almost certainly does. Both for 
sure.

>Does that mean you're not a systemd fan :) ?

I think it's about the most ridiculous thing I've seen. It takes all the 
dumb things about Windows and puts them in Linux.

>Is shibd ready to process requests when it calls
>listener->run(&shibd_shutdown) (shibd.cpp:L442) ? (With forking shibd
>signals parent with SIGUSR1 just before listener->run).

I'd have to research how it all works, but I believe it is. The metadata 
is being loaded in this call:
 
    if (!conf.instantiate(shar_config)) {


Once that's done, the run step is just socket work.

>If calling sd_notify(0, "READY=1") just before listener->run is ok, then
>I can try to create a small patch (with autoconf: --enable-systemd).

It should be.

-- Scott