LEAP timer memory leak

[hafe]

Services using timers like CKPT experience a slow but measurable increase in memory use over time (process ncs_cpnd). Of course depending of the application.

The LEAP timer control block is approximately 64 bytes and will not be returned until the timer has expired. The function ncs_tmr_free() does not free the memory, it just change the state of the timer.

[marioa]

TLC decision: LEAP Timers are used throughout OpenSAF and it was decided that it could be risky to change this code in this phase of project. Recommendation is to retag it for the next release, and hopefully somebody will take initiative and provide patch in early project phases. Recommended workaround for this ticket is to try to have retention times closer to the lifetime of an checkpoint.