When the loading of a dynamic module by the gatekeeper (gridftp probably as
well) fails e.g., due to missing libraries, unresolved symbols present in the
authorization module that is being loaded the gatekeeper fails with a sigsegv
without protocolling the error in the logs.

I would love to see a signal handler for sigsegv that produces a final message
in the log and helps it to fail gracefully if there is a problem with the module
configuration/deployment - it would also alarm the sysadmin toward an existing
problem with this configuration. Also for debugging it would be great if there
would be a non-forking option for the gatekeeper. The option for not detaching
from the terminal exists, but it still does fork a child for each incomming
request. 

I have added this to a GT3.2 gatekeeper by inserting a "if(!foreground) {   }"
around the forking code about at line 1000 of the code. This way if forground is
selected (e.g., via the debug option) the gatekeeper won't fork children and act
as a single request sequential service, easier for debugging segfaults in gdb