strategies for testing module compiled from source

[Cantor, Scott]

On Aug 16, 2013, at 11:56 PM, "Scott Koranda" <skoranda at gmail.com> wrote:
> 
> The shibd daemon starts and appears to run as expected.

For the record, shibd has no dependencies on the web server used, it won't affect the build in any way.

> When OHS is started it appears to start normally and load the module.
> A 'lsof -p' against the process(es) shows that the module .so file is
> opened. Also a zero byte native.log file is created in the configured
> location when OSH starts up.

That's a bad sign, since the log should have something in it. But I don't see how the web server could start up if it doesn't get far enough to write anything to the file.

> What strategies can we pursue to further test that the module is
> properly loaded and "listening"?

Maybe turning up the apache log level. Without getting native.log output, there's nothing else to go by short of a debugger.

I assume the output of /Shibboleth.sso/foo is a 404 from Apache itself. Otherwise something is intercepting the requests before the module has a chance.

-- Scott