[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bayonne-devel] grep dlgnDriver = dialogic or globalcall?
From: |
David Sugar |
Subject: |
Re: [Bayonne-devel] grep dlgnDriver = dialogic or globalcall? |
Date: |
Sat, 19 Jul 2003 06:56:21 -0400 |
User-agent: |
KMail/1.5 |
At some point we will have only one dialogic driver, "globalcall", but the
globalcall driver is not yet ready for that. The old detect routine has no
means to distinguish between the two. At the moment, /etc/sysconfig/bayonne
is the preferred way to specify a driver, with the init script's autodetect
used as a default to automate driver selection.
I remember I at one time had problems with combining the run check, which is
why I originally seperated them...strange...
On Friday 18 July 2003 06:49 pm, Erik Enge wrote:
> Hi.
>
> In /etc/init.d/bayonne (version 1.2.6), I have:
>
> sym=X`lsmod | grep dlgnDriver`X
> if test "$sym" != "XX" ; then
> export BAYONNE_DRIVER=dialogic
> fi
>
> This grep will return successful for me because I do indeed have the
> dlgnDriver insmod'd. However, Bayonne will never run with the
> --dialogic for me as I need --globalcall. Is there a bug somewhere
> here?
>
> Also, in the sbin/bayonne script, I find the following code does not
> work for me:
>
> run=`ps ax`
> run=`echo $run | grep bayonne.bin`
>
> I have worked around it with:
>
> run=`ps ax | grep bayonne.bin`
>
> which seems to work every time so far.
>
> Erik.
>
>
>
> _______________________________________________
> Bayonne-devel mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bayonne-devel