Hi list,
attached is a redirected mail concerning the mutex lock for
bearerbox's internal smsbox routing.
Stipe
[EMAIL PROTECTED]
-------------------------------------------------------------------
Wapme Systems AG
Vogelsanger Weg 80
40470 D�sseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are
--- Begin Message ---
Hi list,
Some days ago my patch for bb_boxc and smsbox race was commited to CVS.
As I didn't use wapbox, I didn't see that wapbox doesn't identify itself to
bearerbox at all.
I think that this patch should influence only smsbox.
This little change solve the problem:
Index: gw/bb_boxc.c
===================================================================
RCS file: /home/cvs/gateway/gw/bb_boxc.c,v
retrieving revision 1.60
diff -u -r1.60 bb_boxc.c
--- gw/bb_boxc.c 23 Jan 2003 23:52:37 -0000 1.60
+++ gw/bb_boxc.c 30 Jan 2003 16:01:20 -0000
@@ -255,7 +255,7 @@
list_add_producer(flow_threads);
/* wait for smsbox identification */
- if (bb_status != BB_DEAD && conn->alive) {
+ if (bb_status != BB_DEAD && conn->alive && conn->is_wap == 0) {
mutex_lock(conn->boxc_id_mutex);
debug("bb.boxc", 0, "boxc_sender: sender unlocked");
}
Please vote and commit it to cvs. I think it may be important for everybody
using wapbox.
Regards
Robert Galach
--- End Message ---
