Hello,

when you run just 'kamailio', the first executable found in path is executed (this is returned by command 'which kamailio'). When you execute with absolute path /etc/init.d/kamailio, then that specific file is executed.

'which kamailio' returns very likely the kamailio binary (/usr/local/sbin/kamailio if you installed from sources), which is the pure kamailio with no command line parameters.

The /etc/init.d/kamailio is a script, wrapper around the pure kamailio binary, giving to it some command line parameters.

If you do 'ps auxw | grep kamailio' you should see the difference of running command.

Cheers,
Daniel

On 2/5/12 9:26 AM, Uri Shacked wrote:

Hi,

 

any help will be graet....

 

 

 hi,
>
> when i moved the /etc/init.d/kamailio file. kamailio did not start at boot.
> now, i set the debug level to 4 and run kamailio in both ways.
>
> 1. "/etc/init.d/kamailio start"
>
  the resault was :

*Feb  1 19:59:04 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:202]: qm_malloc_init: QM_OPTIMIZE=16384, /ROUNDTO=2048
Feb  1 19:59:04 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:204]: qm_malloc_init: QM_HASH_SIZE=2099, qm_block
size=218344
Feb  1 19:59:04 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:205]: qm_malloc_init(0x7f1cf585b000, 2147483648),
start=0x7f1cf585b000
Feb  1 19:59:04 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:213]: qm_malloc_init: size= 2147483648, init_overhead=218440
Feb  1 19:59:04 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/shm_mem.c:203]: shm_mem_init: success*

>
> you can see the shm_mem size is 2048Mb.
>

2."kamailio"
the resault was :

*Feb  1 19:56:50 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:202]: qm_malloc_init: QM_OPTIMIZE=16384, /ROUNDTO=2048
Feb  1 19:56:50 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:204]: qm_malloc_init: QM_HASH_SIZE=2099, qm_block
size=218344
Feb  1 19:56:50 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:205]: qm_malloc_init(0x7f8618310000, 33554432),
start=0x7f8618310000
Feb  1 19:56:50 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:213]: qm_malloc_init: size= 33554432, init_overhead=218440
Feb  1 19:56:50 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/shm_mem.c:203]: shm_mem_init: success*
**
the resault is 32Mb.

any ideas?


>
> On Wed, Feb 1, 2012 at 5:01 PM, Jason Penton <jason.penton at smilecoms.com>wrote:
>
>> I am not familiar with Centos but I suspect there is another script being
>> run from somewhere. What I would do is move the /etc/init.d/kamailio script
>> somewhere safe (your home directory for eg). Then reboot and see if
>> kamailio still starts - if it does you need to find out whihc script is
>> being called and where it is.
>>
>> If you are not running X by default you are prob in runlevel 3. If you
>> are running X, then it will be 5. check where you runlevel scripts are
>> pointing. e.g.
>>
>> ls -al /etc/rc3.d/SXXkamailio (X = [0-9])
>>
>> Cheers
>> Jason
>>
>>  On Wed, Feb 1, 2012 at 4:26 PM, Uri Shacked <uri.shacked at gmail.com>wrote:
>>
>>>  Hi,
>>>
>>> when i reboot the machine, it starts with 32Mb and i do not understand
>>> why...
>>> so, does it use a startup file that i am not familiar with?
>>> what is the appropriate runlevel? how do i set it and where?
>>>
>>> thanks,
>>> Uri
>>>
>>>
>>> >Hi Sammy,
>>> >
>>> >When you use the init script, it is starting Kamailio with the correct
>>> >arguments to get the environment you wish (-m 2048 probably). If
>>> however,
>>> >you just call kamailio these args are not there. Im not sure why you are
>>> >running with kamailio command directly. Why don't you add your init
>>> script
>>> >to the appropriate runlevel for auto startup?
>>> >
>>> >Cheers
>>> >Jason
>>>
>>> On Wed, Feb 1, 2012 at 3:06 PM, Uri Shacked <ushacked at gmail.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
>>> wrote:
>>>
>>> >* Hi again....
>>> *>*
>>> *>* i installed kamailio 3.2.2 today.
>>> *>* i used the chkconfig tool to get kamailio run at boot.
>>> *>* i edited both /etc/init.d/kamailio and /etc/default/kamailio files
>>> to run
>>> *>* with 2048Mg of memory.
>>> *>* now, when i run /etc/init.d/kamailio start, it starts with the right
>>> *>* amount of memory.
>>> *>* when i rum "kamailio" only, it starts with 32Mb....
>>> *>*
>>> *>*  i use centos 6.2 64bit.
>>> *>* any ideas?
>>> *>*
>>> *>*
>>> *>*
>>> *>*
>>> *>*
>>> *>* On Tue, Oct 25, 2011 at 1:18 PM, Uri Shacked <ushacked at gmail.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
>>> wrote:
>>> *>*
>>> *>>* Hi.
>>> *>>* I already checked it all. The kamailio start and stop command did
>>> not
>>> *>>* work. The init script i used was for debian. Now i use another
>>> script,
>>> *>>* for centos. It works. I add the kamailio proccess with chkconfig
>>> tool.
>>> *>>* Thanks.
>>> *>>*
>>> *>>* On 10/25/11, Sammy Govind <govoiper at gmail.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
>>> wrote:
>>> *>>* > Thanks Alex,
>>> *>>* >
>>> *>>* > Hey Uri, can you check if you've /etc/init.d/kamailio file
>>> exists - open
>>> *>>* > that file if exists and cross verify few parameters.
>>> *>>* > Few of these are as follows
>>> *>>* >
>>> *>>* > PATH=/sbin:/bin:/usr/sbin:/usr/bin
>>> *>>* > DAEMON=*/usr/local/sbin/kamailio*
>>> *>>* > NAME=kamailio
>>> *>>* > DESC=kamailio
>>> *>>* > HOMEDIR=/var/run/
>>> *>>* > *PIDFILE*=$HOMEDIR/$NAME.pid
>>> *>>* > DEFAULTS=*/etc/default/kamailio.default*
>>> *>>*  > RUN_KAMAILIO=yes
>>> *>>* >
>>> *>>* > Make sure /etc/default/kamailio.default file exits. here are the
>>> *>>* contents of
>>> *>>* > my file.
>>> *>>* >
>>> *>>* > RUN_KAMAILIO=yes
>>> *>>* > USER=kamailio
>>> *>>* > GROUP=kamailio
>>> *>>* > MEMORY=64
>>> *>>* > DUMP_CORE=no
>>> *>>* >
>>> *>>* > On Tue, Oct 25, 2011 at 3:38 AM, Klaus Darilion <
>>> *>>* > klaus.mailinglists at pernau.at<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
>>> wrote:
>>> *>>* >
>>> *>>* >> Test the startupscript if they work:
>>> *>>* >>
>>> *>>* >> /etc/init.d/kamailio start
>>> *>>* >> /etc/init.d/kamailio stop
>>> *>>* >>
>>> *>>* >> If this works, then make sure to have proper symlinks from the
>>> *>>* >> corresponding runlevel to the startup script. Do it manually or
>>> use the
>>> *>>* >> chkconfig tool.
>>> *>>* >>
>>> *>>* >> klaus
>>> *>>* >>
>>> *>>* >>
>>> *>>* >> On 24.10.2011 08:00, Uri Shacked wrote:
>>> *>>* >>
>>> *>>* >>> hi again,
>>> *>>* >>> i found out that on my centos 5.4 the command
>>> start-stop-daemon that
>>> *>>* the
>>> *>>* >>> /etc/init.d/kamailio uses is not recognized.
>>> *>>* >>> it is kamailio3.2 any ideas?
>>> *>>* >>>
>>> *>>* >>>
>>> *>>* >>> On Mon, Oct 24, 2011 at 3:03 PM, Uri Shacked <ushacked at
>>> gmail.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
>>> *>>* >>> <mailto:ushacked at gmail.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>>
>>> wrote:
>>> *>>* >>>
>>> *>>* >>>    Hi,
>>> *>>* >>>    what is the best way to start kamailio at boot?
>>> *>>* >>>    the example in the install is not working for me....
>>> *>>* >>>
>>> *>>* >>>
>>> *
>>>
>>
>> This email is subject to the disclaimer of Smile Communications (PTY) Ltd. at http://www.smilecoms.com/disclaimer
>>
>>
>

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda