Hi Jelle. Actually linux shows you each thread of each process like an independent process, but you have one process for bearerbox and one process for smsbox there (I recommend you to read http://www.kannel.org/download/1.2.1/arch-1.2.1/arch.html, specially http://www.kannel.org/download/1.2.1/arch-1.2.1/arch.html#AEN294). The number of threads in bearerbox is dependant, as an example, on the number of connections to smscs and other kannel's boxes (two threads are created in bearerbox for each connection to a wapbox or smsbox); there is a thread that writes the store file too, etc. You can see the creation of each thread in the output (DEBUG verbosity). For example:
2006-02-09 12:52:49 [6464] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2006-02-09 12:52:49 [6464] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2006-02-09 12:52:49 [6464] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2006-02-09 12:52:49 [6464] [0] DEBUG: starting UDP sender/receiver module 2006-02-09 12:52:49 [6464] [0] INFO: Adding interface 172.16.58.24 2006-02-09 12:52:49 [6464] [0] DEBUG: udpc_create: Bound to UDP <172.16.58.24:9200> 2006-02-09 12:52:49 [6466] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 6466. 2006-02-09 12:52:49 [6467] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 6467. 2006-02-09 12:52:49 [6468] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 6468. 2006-02-09 12:52:49 [6464] [0] DEBUG: Started thread 4 (gw/bb_udp.c:udp_receiver) 2006-02-09 12:52:49 [6464] [0] DEBUG: Started thread 5 (gw/bb_udp.c:udp_sender) 2006-02-09 12:52:49 [6464] [0] DEBUG: udpc_create: Bound to UDP <172.16.58.24:9201> 2006-02-09 12:52:49 [6469] [4] DEBUG: Thread 4 (gw/bb_udp.c:udp_receiver) maps to pid 6469. 2006-02-09 12:52:49 [6470] [5] DEBUG: Thread 5 (gw/bb_udp.c:udp_sender) maps to pid 6470. 2006-02-09 12:52:49 [6464] [0] DEBUG: Started thread 6 (gw/bb_udp.c:udp_receiver) 2006-02-09 12:52:49 [6471] [6] DEBUG: Thread 6 (gw/bb_udp.c:udp_receiver) maps to pid 6471. 2006-02-09 12:52:49 [6464] [0] DEBUG: Started thread 7 (gw/bb_udp.c:udp_sender) 2006-02-09 12:52:49 [6464] [0] DEBUG: starting wapbox connection module 2006-02-09 12:52:49 [6464] [0] DEBUG: Started thread 8 (gw/bb_boxc.c:wdp_to_wapboxes) 2006-02-09 12:52:49 [6472] [7] DEBUG: Thread 7 (gw/bb_udp.c:udp_sender) maps to pid 6472. 2006-02-09 12:52:49 [6473] [8] DEBUG: Thread 8 (gw/bb_boxc.c:wdp_to_wapboxes) maps to pid 6473. 2006-02-09 12:52:49 [6464] [0] DEBUG: Started thread 9 (gw/bb_boxc.c:wapboxc_run) 2006-02-09 12:52:49 [6464] [0] DEBUG: starting WDP router 2006-02-09 12:52:49 [6474] [9] DEBUG: Thread 9 (gw/bb_boxc.c:wapboxc_run) maps to pid 6474. 2006-02-09 12:52:49 [6464] [0] DEBUG: Started thread 10 (gw/bearerbox.c:wdp_router) 2006-02-09 12:52:49 [6464] [0] INFO: ---------------------------------------- 2006-02-09 12:52:49 [6464] [0] INFO: Kannel bearerbox II version cvs-20051013 starting 2006-02-09 12:52:49 [6464] [0] INFO: Loading store file `/var/run/kannel.store' 2006-02-09 12:52:49 [6464] [0] INFO: Store-file size 571, starting to unpack 2006-02-09 12:52:49 [6464] [0] INFO: Retrieved 2 messages, non-acknowledged messages: 2 2006-02-09 12:52:49 [6464] [0] DEBUG: Started thread 11 (gw/bb_store.c:store_dumper) 2006-02-09 12:52:49 [6464] [0] INFO: MAIN: Start-up done, entering mainloop 2006-02-09 12:52:49 [6475] [10] DEBUG: Thread 10 (gw/bearerbox.c:wdp_router) maps to pid 6475. 2006-02-09 12:52:49 [6476] [11] DEBUG: Thread 11 (gw/bb_store.c:store_dumper) maps to pid 6476. 2006-02-09 12:53:09 [6476] [11] DEBUG: Dumping 2 messages to store This is linux too: you can see the messages indicating thread creation and the pid associated with the new thread (again, not the pid of a real process). Each line in the log indicates, in order: date and time, process id, thread number, level of the message and finally the actual message. So, the number of processes (threads), is not hard coded, but it depends directly on your setup. No additional threads are created because of the number of incoming sms or HTTP requests or anything like that, tough (like it would happen with Apache). Cheers Juan On 2/9/06, Jelle S. <[EMAIL PROTECTED]> wrote: > Hi list, > > Kannel is running fine just a question about the amount of processes > running. > I'm running kannel-1.4.0 on a Gentoo Linux system. > > > When checking the amount of processes running I get this: > > > kannel 11392 1 0 12:55 ? 00:00:00 /usr/sbin/bearerbox > --verbosity 0 --logfile /tmp/bearerbox.log /etc/kannel/kannel.conf > kannel 11394 11392 0 12:55 ? 00:00:00 /usr/sbin/bearerbox > --verbosity 0 --logfile /tmp/bearerbox.log /etc/kannel/kannel.conf > kannel 11395 11394 0 12:55 ? 00:00:00 /usr/sbin/bearerbox > --verbosity 0 --logfile /tmp/bearerbox.log /etc/kannel/kannel.conf > kannel 11396 11394 0 12:55 ? 00:00:00 /usr/sbin/bearerbox > --verbosity 0 --logfile /tmp/bearerbox.log /etc/kannel/kannel.conf > kannel 11397 11394 0 12:55 ? 00:00:00 /usr/sbin/bearerbox > --verbosity 0 --logfile /tmp/bearerbox.log /etc/kannel/kannel.conf > kannel 11398 11394 0 12:55 ? 00:00:00 /usr/sbin/bearerbox > --verbosity 0 --logfile /tmp/bearerbox.log /etc/kannel/kannel.conf > kannel 11399 11394 0 12:55 ? 00:00:00 /usr/sbin/bearerbox > --verbosity 0 --logfile /tmp/bearerbox.log /etc/kannel/kannel.conf > kannel 11400 11394 0 12:55 ? 00:00:00 /usr/sbin/bearerbox > --verbosity 0 --logfile /tmp/bearerbox.log /etc/kannel/kannel.conf > kannel 11401 11394 0 12:55 ? 00:00:00 /usr/sbin/bearerbox > --verbosity 0 --logfile /tmp/bearerbox.log /etc/kannel/kannel.conf > kannel 11409 1 0 12:56 ? 00:00:00 /usr/sbin/smsbox > --verbosity 1 --logfile smsbox.log /etc/kannel/kannel.conf > kannel 11410 11409 0 12:56 ? 00:00:00 /usr/sbin/smsbox > --verbosity 1 --logfile smsbox.log /etc/kannel/kannel.conf > kannel 11411 11410 0 12:56 ? 00:00:00 /usr/sbin/smsbox > --verbosity 1 --logfile smsbox.log /etc/kannel/kannel.conf > kannel 11412 11410 0 12:56 ? 00:00:00 /usr/sbin/smsbox > --verbosity 1 --logfile smsbox.log /etc/kannel/kannel.conf > kannel 11413 11410 0 12:56 ? 00:00:00 /usr/sbin/smsbox > --verbosity 1 --logfile smsbox.log /etc/kannel/kannel.conf > kannel 11414 11410 0 12:56 ? 00:00:00 /usr/sbin/smsbox > --verbosity 1 --logfile smsbox.log /etc/kannel/kannel.conf > kannel 11415 11410 0 12:56 ? 00:00:00 /usr/sbin/smsbox > --verbosity 1 --logfile smsbox.log /etc/kannel/kannel.conf > kannel 11416 11410 0 12:56 ? 00:00:00 /usr/sbin/smsbox > --verbosity 1 --logfile smsbox.log /etc/kannel/kannel.conf > kannel 11417 11394 0 12:56 ? 00:00:00 /usr/sbin/bearerbox > --verbosity 0 --logfile /tmp/bearerbox.log /etc/kannel/kannel.conf > kannel 11418 11394 0 12:56 ? 00:00:00 /usr/sbin/bearerbox > --verbosity 0 --logfile /tmp/bearerbox.log /etc/kannel/kannel.conf > kannel 11419 11410 0 12:56 ? 00:00:00 /usr/sbin/smsbox > --verbosity 1 --logfile smsbox.log /etc/kannel/kannel.conf > This makes 11 processes Bearerbox > and 9 processes smsbox, > > Does the amount of processes change for some reason whenever? > Are these amounts hardcoded into kannel? > Is there a possibility to fiddle around with this? > > Thanks in advance > > Jelle. > > -- Juan
