Hi, On Thu, Dec 10, 2015 at 3:18 PM, ValdikSS <i...@valdikss.org.ru> wrote:
> Use dynamic sessions. > > Many applications add filtering policy objects at start, and then delete > these objects at stop. By using a dynamic session, you guarantee that these > objects are deleted even if the application crashes. Furthermore, simply > closing the engine handle at stop is more efficient than making individual > calls to delete each object. > > Going by that just closing the engine appears good enough. I never tested really changing the tapluid between a SIGHUP restart (how to trigger that) to know whether any old filters hang around after a _uninit. Anyway, those are very unlikely cases and we cant guarad against everything up front. I would say go for v9 with a simple closing of the engine. Thanks, Selva
