i will try to do tests, but i want to show the differences between files:

[EMAIL PROTECTED]:~/kannel/gateway$ diff ../gateway-my/gw/smsc/smsc_cimd2.c 
gw/smsc/smsc_cimd2.c
2071c2071
<     double    sleep = 0.0001;
---
>     double    sleep;
2099a2100,2101
>         sleep = 0.0001;
>
2121d2122
<
2133,2135d2133
<         }
<         else {
<             sleep = 0.0001;

here "../gateway-my/gw/smsc/smsc_cimd2.c" is the file, which "works fine"
and "gw/smsc/smsc_cimd2.c" is the file from current CVS.

regards,
Dziugas Baltrunas

On Mon, 31 Mar 2003, Angel Fradejas wrote:

> Everything it's ok --apart from the different MD5 ;-)
>
> Try with the same debug message you put last time. On an idle cnx you'd have
> a loop every 2 seconds after a short period of stabilization.
>
> /Angel.
>
> -----Mensaje original-----
> De: Dziugas Baltrunas [mailto:[EMAIL PROTECTED]
> Enviado el: lunes 31 de marzo de 2003 17:06
> Para: Angel Fradejas
> CC: Stipe Tolj; [EMAIL PROTECTED]
> Asunto: RE: [PATCH] smsc_cimd2.c sleep times
>
>
> here are my steps:
>
> 1) [EMAIL PROTECTED]:~/kannel/gateway$ rm gw/smsc/smsc_cimd2.c
> 2) [EMAIL PROTECTED]:~/kannel/gateway$ cvs update -d
> 3) [EMAIL PROTECTED]:~/kannel/gateway$ gmake clean
> 4) [EMAIL PROTECTED]:~/kannel/gateway$ ./configure --with-cflags="-pthread"
> 5) [EMAIL PROTECTED]:~/kannel/gateway$ gmake
> 6) [EMAIL PROTECTED]:~/kannel/gateway$ sudo bash
> 7) [EMAIL PROTECTED]:~/kannel/gateway$ gmake install
> 8) [EMAIL PROTECTED]:~/kannel/gateway$ /usr/local/etc/rc.d/kannel.sh stop
> 9) [EMAIL PROTECTED]:~/kannel/gateway$ /usr/local/etc/rc.d/kannel.sh start
>
> here is top output:
>
>   PID USERNAME PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU COMMAND
> 51838 root      64   0  6268K  3200K RUN      2:47 99.00% 98.97% bearerbox
>
> am I doing something wrong? correct please ;)
>
> regards,
> Dziugas Baltrunas
>
> On Mon, 31 Mar 2003, Angel Fradejas wrote:
>
> > >> >MD5 (gw/smsc/smsc_cimd2.c) = e1a4a3d6d621e3d35a9e5e3b818f58c5
> > >
> > >> bde1aad2fbf65994141b60e672ae9777  gw/smsc/smsc_cimd2.c
> > >
> > >so obviosly you guys have the following:
> > >
> > >a. not the same smsc_cimd2.c
> > >b. not the same MD5 algorithm
> >
> > Good logic Stipe ;)))
> >
> > /Angel.
> >
>

Reply via email to