[asterisk-dev] shutting down zaptel spans
Tzafrir Cohen
tzafrir.cohen at xorcom.com
Thu Sep 28 01:38:34 MST 2006
In the init.d script of the Debian zaptel package the "stop" target is
empty. However other scripts seems to do awful lot of work there.
Is there a point in actively removing the zaptel modules at system
shutdown? Apart from wasting time and optionally hanging the system[0]?
When is there a need to shut down zaptel spans from userspace?
Cases I'm aware of:
* Something related to dynamic spans. Not sure exactly why.
* I understand that some PRI cards require that. If so: why? Can't a
driver tell that it is being removed and shut itself down?
----
[0] Debugging a failure in the system shutdown scripts is tough, because
there is not guaranteed place to log to. And it is quite easy to miss
the messages. Hence think carefully about adding unnecessary operations
at system shutdown.
I have seen too many badly-written zaptel modules whose problem is
manufested at rmmod time. Nobody debugs that ;-)
--
Tzafrir Cohen sip:tzafrir at local.xorcom.com
icq#16849755 iax:tzafrir at local.xorcom.com
+972-50-7952406 jabber:tzafrir at jabber.org
tzafrir.cohen at xorcom.com http://www.xorcom.com
More information about the asterisk-dev
mailing list