Thanks. That makes a lot of sense. Looking at the output of my ps -ax, each
process appears to have been allocated 2048M of memory. I was trying to
start OpenSIPS with 2048M of memory allocated to the shared pool using
the "-m 2048" startup flag. Did I accomplish this, or did I actually
allocate 2048 x process threads?
Geoff
On Nov 9, 2008 3:21pm, Schumann Sebastian <[EMAIL PROTECTED]>
wrote:
Hi
You can check the processes in detail using the FIFO command
$ opensipsctl fifo ps
(FIFO must be enabled).
The processes are almost as Inaki described.
In detail, it should be like this:
1. UDP WORKER (SIP) x children x interfaces
children=10
listen=10.0.0.1:5060
listen=10.0.0.2:5060
-> 20 processes finally, so children for each interface
2. TCP WORKER (SIP) x children
tcp_children=5
listen....... does not matter, fixed number of processes handles it. If
no tcp_children is set and TCP enabled, the children number is used.
--> 5 processes
3. TCP MANAGER x1
4. TIMER PROCESSES (multiple possible)
5. ATTENDANT x1
Sometimes, also modules can require additional processes.
Sebastian
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Iñaki Baz Castillo
Sent: Sun 11/9/2008 21:13
To: [email protected]
Subject: Re: [OpenSIPS-Users] Process List Question
El Domingo, 9 de Noviembre de 2008, Geoffrey Mina escribió:
> I just installed OpenSIPS and got everything up and running. Can
somebody
> please explain the output of "ps -ax" to me? I don't understand why
there
> are so many processes running.
>
>
> [EMAIL PROTECTED] log]# ps ax | grep opensips
> 29371 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29373 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29374 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29375 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29376 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29377 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29378 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29379 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29380 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29381 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29382 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29383 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29384 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29385 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29386 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29387 ? S 0:00 /usr/local/sbin/opensips -m 2048
> 29470 pts/0 S+ 0:00 grep opensips
It depends on the number of interfaces and transport protocol (TCP/UDP) in
which opensips is listening. If you set "children=4" and listen in eth0
for
TCP and UDP then you will have 4*2 + main process = 9 (well, it's
something
like this but not exactly).
--
Iñaki Baz Castillo
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
