ztcfg at asterisk init.d script

[Kilian Krause]

--=-bBQ6Tjt8eTrFq/S5lajs
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi Tzafrir,

Am Donnerstag, den 17.02.2005, 13:46 +0200 schrieb Tzafrir Cohen:
> The current asterisk init.d script suggests that ztcfg could be run from
> the asterisk init.d script:
>=20
> # Additional commands
> # put additional commands here like
> #
> #rmmod zaphfc
> #modprobe zaphfc modes=3D1
> #/usr/sbin/ztcfg -v >/dev/null
>=20
> Would you consider it surprising if those modules are loaded at asterisk
> startup?

well, that's a *VERY* crude hack that's for now needed with zaphfc. Long
term i seek to replace that need to enforce having ztcfg only run *ONCE*
by making the zaphfc patch work correctly. Just for now it's a somewhat
more meaningful place to ensure that ztcfg isn't run multiple before
starting asterisk. For the version to upload i'm also not entirely sure
if i'd leave this in. I wish Santiago would get back to me to discuss
the zaphfc issue.=20

I hope this explains a bit why this is where i put it. Also I won't
force nobody to remove the hashmarks before there, it's just a
WorksForMe(TM) in some more foolproof manner than /etc/modules. If you
feel like providing a patch for zaphfc that does ignore the subsequent
calls of ztcfg once the zaphfc module is initialized, feel free to mail
it directly to me (as zaphfc patches aren't in Debian now, please don't
file a bug).

--=20
Best regards,
 Kilian

--=-bBQ6Tjt8eTrFq/S5lajs
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCFRqjvdkzt4X+wX8RApPwAJwMAuy+TCC9CXmQPEiENIXTIR2YawCdE6Dg
MIwNCMfY5CMByhjKqnUOSZQ=
=IRDk
-----END PGP SIGNATURE-----

--=-bBQ6Tjt8eTrFq/S5lajs--