🚀 go-pugleaf

I'm having a problem adding a new service to the services that run on isode.
I've modified ftamd.c so that running $(ETCDIR)iso.ftam (the ftam responder)
with -s qualifier sets an internal variable, security. A similar modification
has been made to ftam.c. Calling ftam from BINDIR with a -s tag sets security
in the local ftam routines. Then I changed ftaminitiate.c so that it sets its
context to be 'secure_ftam' instead of "iso ftam' when security is set.
 To allow this to take place
I added lines to the isobjects, isoentities, and isoservices database files.
The program to be called (the last variable in the new line in the isoservices
 file) is defined to be "iso.ftam -s". This is all described in section 10.1 of
volume 1 of thew manual. 

Has anyone done somehing similar successfully  ? Are there any pitfalls I may
have fallen into ? Where in the code might I put checkpoints to tell me what
entities and services are _actually_ being invoked ?

Any help will be most gratefully received

Ciaran

----------------------------------------------------------------------------
Ciaran Clissmann              .     Self-fulfillment is not important, so long
Dept Computer Science         .     as you get what you want out of life
University College Dublin     .
Ireland                       .