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

[Cantor, Scott]

On 6/8/15, 4:15 AM, "users on behalf of Jarno Huuskonen" <users-bounces at shibboleth.net on behalf of jarno.huuskonen at uef.fi> wrote:

>I've been using this shibd.service file with rhel7/centos7 and it
>seems to work just fine. AFAIK with -F (shibd doesn't fork) the wait
>timeout is ignored. So too short -w timeout shouldn't be a problem.

I don't think that's ideal for the reasons already noted. shibd used to operate that way and it was changed pretty deliberately.

>(NOTE: I'm not sure if /run/shibboleth matches the directory that shibd
>uses by default (I'm using customized rpms/config)).

Runtime files are in /var/run/shibboleth.

>I think that systemd/shibd integration could be improved:
>with systemd use SD_INFO / SD_ERR / SD_CRIT when writing errors(from
>shibd.cpp) to stderr
>(http://www.freedesktop.org/software/systemd/man/sd-daemon.html)
>and
>call sd_notify(0, "READY=1"); / sd_notify(0, "STOPPING=1"); when
>starting / stopping
>(http://www.freedesktop.org/software/systemd/man/sd_notify.html).
>(with sd_notify READY=1, the shibd.service could use TimeoutStartSec=).

Well, conditionally I suppose. There are too many platforms without it and hopefully this is all temporary and somebody regains their sanity.

>I can send a patch for this if this sounds reasonable ?

You can attach any patches suggested to SSPCPP-412, provided our contribution policy is met. [1]

But I will say in this case that a working autoconf patch is also a precondition. I'm not going to spend any time on that, and this is all conditional code.

-- Scott

[1] https://wiki.shibboleth.net/confluence/display/DEV/Contribution+Policy