[Serdev] [Tracker] Closed: (SER-105) ser -c : clash mod_init/child_init and mod_exit calls

[Andrei Pelinescu - Onciul (JIRA)]

     [ http://tracker.iptel.org/browse/SER-105?page=all ]

Andrei Pelinescu - Onciul closed SER-105.
-----------------------------------------

    Resolution: Won't Fix

IMHO the mod_exit functions must be called even if mod_init was not (for example to be able to free resources allocated in fixup functions).  ser -c should not cause the mod_init functions to be run, some modules might try to fork, open sockets, files or connections to DBs from mod_init and this should not happend for a simple config check. We need another switch ( -cc ?) for checking the config + init, but for future releases (not Ottendorf).

> ser -c : clash mod_init/child_init and mod_exit calls
> -----------------------------------------------------
>
>                 Key: SER-105
>                 URL: http://tracker.iptel.org/browse/SER-105
>             Project: SER
>          Issue Type: Bug
>          Components: core
>    Affects Versions: Ottendorf
>            Reporter: Michal Matyska
>         Assigned To: Andrei Pelinescu - Onciul
>            Priority: Trivial
>             Fix For: Ottendorf
>
>
> If you start ser with -c parameter to check the config file, the mod_exit function is beeing called (due to the signal handling, when ser exits), whilst the mod_init/child_init were NOT called (and some script rrors, which show up at mod_init/child_init fixup/parsing etc, won't be discovered).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.iptel.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira