shibd Aborted, No Error in Logs

[Cantor, Scott]

> I wonder, when shibd communicates over TCP/IP sockets, usually
> listening on localhost (127.0.0.1) at a configured port.

No. The shibd daemon is not supported for use over a network and a domain socket is faster and that's why it's the default. TCP is only there to support Windows, where domain sockets aren't supported.

> No socket file (like /var/run/shibboleth/socket) is created unless
> explicitly configured to use a Unix socket

That is true, yes, but it is not appropriate to run it any other way on Linux.

> Shibboleth2.xml configured using 

That's just not viable. In addition to being insecure, it will scale horribly, and it certainly won't help with stability, and that is not a supported confguration. That is not a change.

BTW stackSize="0" makes no sense, I would assume that does nothing and the stack size would default, which is also too large for a loaded system most of the time and will crash it if it gets enough traffic.

-- Scott