On Thu, Sep 11, 2008 at 05:29:44PM +0200, David Paleino wrote: > > I wonder how this can be done with zaptel. If you try to be > > user-friendly and run '/etc/init.d/zaptel/unload' when installing > > zaptel-modules-<current-kernel>' it'll eventually fail normally, because > > Asterisk holds /dev/zap/pseudo open, and hence zaptel cannot be > > unloaded. > > > > (And this assumes that the application using it is 'asterisk') > > I believe this is a bug in the zaptel init scripts... shouldn't they check > whether they can be unloaded? Is there a --force option? But this is another > story :)
Maybe it's possible (I'm not exactly sure. I think it's possible, at least in most cases). But do I want this? Do I want to shut down my PBX because of the Ubuntu kernel upgrade of the month? Which is why I never tried to add such an option to the init script, and why noone has asked for it. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il | | a Mutt's [EMAIL PROTECTED] | | best ICQ# 16849754 | | friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]