@@ -227,7 +227,7 @@ bm_log_timer("test");

    Example 1.6. Enabling a timer

 ...

-openserctl fifo bm_enable_timer test 1

+kamctl fifo bm_enable_timer test 1

 ...

 1.6.3. bm_granularity

@@ -280,7 +280,7 @@ bm_log_timer("test");

 				<title>Enabling a timer</title>

 				<programlisting format="linespecific">

 ...

-openserctl fifo bm_enable_timer test 1

+kamctl fifo bm_enable_timer test 1

 ...

 </programlisting>

 			</example>

@@ -873,7 +873,7 @@ reply_code, dstavp)

    Example 1.38. cr_replace_host usage

 ...

-openserctl fifo cr_replace_host "-d proxy -p 49 -h proxy1 -t proxy2"

+kamctl fifo cr_replace_host "-d proxy -p 49 -h proxy1 -t proxy2"

 ...

 1.5.4. cr_deactivate_host

@@ -895,7 +895,7 @@ openserctl fifo cr_replace_host "-d proxy -p 49 -h proxy1 -t proxy2"

    Example 1.39. cr_deactivate_host usage

 ...

-openserctl fifo cr_deactivate_host "-d proxy -p 49 -h proxy1"

+kamctl fifo cr_deactivate_host "-d proxy -p 49 -h proxy1"

 ...

 1.5.5. cr_activate_host

@@ -911,7 +911,7 @@ openserctl fifo cr_deactivate_host "-d proxy -p 49 -h proxy1"

    Example 1.40. cr_activate_host usage

 ...

-openserctl fifo cr_activate_host "-d proxy -p 49 -h proxy1"

+kamctl fifo cr_activate_host "-d proxy -p 49 -h proxy1"

 ...

 1.5.6. cr_add_host

@@ -931,7 +931,7 @@ openserctl fifo cr_activate_host "-d proxy -p 49 -h proxy1"

    Example 1.41. cr_add_host usage

 ...

-openserctl fifo cr_add_host "-d proxy -p 49 -h proxy1 -w 0.25"

+kamctl fifo cr_add_host "-d proxy -p 49 -h proxy1 -w 0.25"

 ...

 1.5.7. cr_delete_host

@@ -952,7 +952,7 @@ openserctl fifo cr_add_host "-d proxy -p 49 -h proxy1 -w 0.25"

    Example 1.42. cr_delete_host usage

 ...

-openserctl fifo cr_delete_host "-d proxy -p 49 -h proxy1 -w 0.25"

+kamctl fifo cr_delete_host "-d proxy -p 49 -h proxy1 -w 0.25"

 ...

 1.6. Examples

@@ -1169,7 +1169,7 @@ cr_tree_rewrite_uri(tree, domain)

 		<title><function>cr_replace_host</function> usage</title>

 		<programlisting format="linespecific">

 ...

-openserctl fifo cr_replace_host "-d proxy -p 49 -h proxy1 -t proxy2"

+kamctl fifo cr_replace_host "-d proxy -p 49 -h proxy1 -t proxy2"

 ...

 		</programlisting>

 	    </example>

@@ -1202,7 +1202,7 @@ openserctl fifo cr_replace_host "-d proxy -p 49 -h proxy1 -t proxy2"

 		<title><function>cr_deactivate_host</function> usage</title>

 		<programlisting format="linespecific">

 ...

-openserctl fifo cr_deactivate_host "-d proxy -p 49 -h proxy1"

+kamctl fifo cr_deactivate_host "-d proxy -p 49 -h proxy1"

 ...

 		</programlisting>

 	    </example>

@@ -1229,7 +1229,7 @@ openserctl fifo cr_deactivate_host "-d proxy -p 49 -h proxy1"

 		<title><function>cr_activate_host</function> usage</title>

 		<programlisting format="linespecific">

 ...

-openserctl fifo cr_activate_host "-d proxy -p 49 -h proxy1"

+kamctl fifo cr_activate_host "-d proxy -p 49 -h proxy1"

 ...

 		</programlisting>

 	    </example>

@@ -1272,7 +1272,7 @@ openserctl fifo cr_activate_host "-d proxy -p 49 -h proxy1"

 		<title><function>cr_add_host</function> usage</title>

 		<programlisting format="linespecific">

 ...

-openserctl fifo cr_add_host "-d proxy -p 49 -h proxy1 -w 0.25"

+kamctl fifo cr_add_host "-d proxy -p 49 -h proxy1 -w 0.25"

 ...

 		</programlisting>

 	    </example>

@@ -1316,7 +1316,7 @@ openserctl fifo cr_add_host "-d proxy -p 49 -h proxy1 -w 0.25"

 		<title><function>cr_delete_host</function> usage</title>

 		<programlisting format="linespecific">

 ...

-openserctl fifo cr_delete_host "-d proxy -p 49 -h proxy1 -w 0.25"

+kamctl fifo cr_delete_host "-d proxy -p 49 -h proxy1 -w 0.25"

 ...

 		</programlisting>

 	    </example>

@@ -334,7 +334,7 @@ shm_status();

    Example 1.14. rand_set_prob usage

 ...

-$ openserctl fifo rand_set_prob 10

+$ kamctl fifo rand_set_prob 10

 ...

 1.5.2. rand_reset_prob

@@ -345,7 +345,7 @@ $ openserctl fifo rand_set_prob 10

    Example 1.15.  rand_reset_prob usage

 ...

-$ openserctl fifo rand_reset_prob

+$ kamctl fifo rand_reset_prob

 ...

 1.5.3. rand_get_prob

@@ -356,7 +356,7 @@ $ openserctl fifo rand_reset_prob

    Example 1.16. rand_get_prob usage

 ...

-$ openserctl fifo get_prob

+$ kamctl fifo get_prob

 The actual probability is 50 percent.

 ...

@@ -372,7 +372,7 @@ The actual probability is 50 percent.

    Example 1.17. check_config_hash usage

 ...

-$ openserctl fifo check_config_hash

+$ kamctl fifo check_config_hash

 The actual config file hash is identical to the stored one.

 ...

@@ -385,7 +385,7 @@ The actual config file hash is identical to the stored one.

    Example 1.18. get_config_hash usage

 ...

-$ openserctl fifo get_config_hash

+$ kamctl fifo get_config_hash

 1580a37104eb4de69ab9f31ce8d6e3e0

 ...

@@ -409,7 +409,7 @@ $ openserctl fifo get_config_hash

    Example 1.19. shv_set usage

 ...

-$ openserctl fifo shv_set debug int 0

+$ kamctl fifo shv_set debug int 0

 ...

 1.5.7. shv_get

@@ -427,8 +427,8 @@ $ openserctl fifo shv_set debug int 0

    Example 1.20. shv_get usage

 ...

-$ openserctl fifo shv_get debug

-$ openserctl fifo shv_get

+$ kamctl fifo shv_get debug

+$ kamctl fifo shv_get

 ...

 1.6. Exported pseudo-variables

@@ -382,7 +382,7 @@ shm_status();

 				<title><function moreinfo="none">rand_set_prob</function> usage</title>

 				<programlisting format="linespecific">

 ...

-$ openserctl fifo rand_set_prob 10

+$ kamctl fifo rand_set_prob 10

 ...

 </programlisting>

 			</example>

@@ -401,7 +401,7 @@ $ openserctl fifo rand_set_prob 10

 					<function moreinfo="none">rand_reset_prob</function> usage</title>

 				<programlisting format="linespecific">

 ...

-$ openserctl fifo rand_reset_prob

+$ kamctl fifo rand_reset_prob

 ...

 </programlisting>

 			</example>

@@ -418,7 +418,7 @@ $ openserctl fifo rand_reset_prob

 				<title><function moreinfo="none">rand_get_prob</function> usage</title>

 				<programlisting format="linespecific">

 ...

-$ openserctl fifo get_prob

+$ kamctl fifo get_prob

 The actual probability is 50 percent.

 ...

 </programlisting>

@@ -438,7 +438,7 @@ The actual probability is 50 percent.

 				<title><function moreinfo="none">check_config_hash</function> usage</title>

 				<programlisting format="linespecific">

 ...

-$ openserctl fifo check_config_hash

+$ kamctl fifo check_config_hash

 The actual config file hash is identical to the stored one.

 ...

 </programlisting>

@@ -457,7 +457,7 @@ The actual config file hash is identical to the stored one.

 				<title><function moreinfo="none">get_config_hash</function> usage</title>

 				<programlisting format="linespecific">

 ...

-$ openserctl fifo get_config_hash

+$ kamctl fifo get_config_hash

 1580a37104eb4de69ab9f31ce8d6e3e0

 ...

 </programlisting>

@@ -495,7 +495,7 @@ $ openserctl fifo get_config_hash

 			<title><function moreinfo="none">shv_set</function> usage</title>

 			<programlisting format="linespecific">

 ...

-$ openserctl fifo shv_set debug int 0

+$ kamctl fifo shv_set debug int 0

 ...

 </programlisting>

 			</example>

@@ -522,8 +522,8 @@ $ openserctl fifo shv_set debug int 0

 			<title><function moreinfo="none">shv_get</function> usage</title>

 			<programlisting format="linespecific">

 ...

-$ openserctl fifo shv_get debug

-$ openserctl fifo shv_get

+$ kamctl fifo shv_get debug

+$ kamctl fifo shv_get

 ...

 </programlisting>

 			</example>

@@ -41,7 +41,7 @@ Will Quan

         1.9. METADATA_KEYS (required)

         1.10. METADATA_READONLY (optional)

         1.11. METADATA_LOGFLAGS (optional)

-        1.12. DB Maintaince Script : openserdbctl

+        1.12. DB Maintaince Script : kamdbctl

         1.13. DB Recovery : bdb_recover

         1.14. Known Limitations

@@ -55,7 +55,7 @@ Will Quan

    1.6. METADATA_COLUMNS

    1.7. METADATA_KEYS

    1.8. METADATA_LOGFLAGS

-   1.9. openserdbctl

+   1.9. kamdbctl

    1.10. bdb_recover usage

 Chapter 1. Admin Guide

@@ -147,7 +147,7 @@ modparam("db_berkeley", "journal_roll_interval", 3600)

    Parameters: tablename (or db_path); to reload a particular

    table provide the tablename as the arguement (eg subscriber);

    to reload all tables provide the db_path to the db files. The

-   path can be found in openserctlrc DB_PATH variable.

+   path can be found in kamctlrc DB_PATH variable.

 1.6. Installation and Running

@@ -175,18 +175,18 @@ modparam("db_berkeley", "journal_roll_interval", 3600)

    install as root user of the main directory. This will install

    the binaries in /usr/local/sbin/. If this was successful,

    openser control engine files should now be installed as

-   /usr/local/sbin/openserdbctl.

+   /usr/local/sbin/kamdbctl.

    Decide where (on the filesystem) you want to install the

    Berkeley DB files. For instance,

    '/usr/local/etc/openser/db_berkeley' directory. Make note of

-   this directory as we need to add this path to the openserctlrc

+   this directory as we need to add this path to the kamctlrc

    file. Note: OpenSER will not startup without these DB files.

-   Edit openserctlrc - There are two parameters in this file that

+   Edit kamctlrc - There are two parameters in this file that

    should be configured before openserctrdb script can work

    properly: DBENGINE and DB_PATH. Edit file:

-   '/usr/local/etc/openser/openserctlrc'

+   '/usr/local/etc/openser/kamctlrc'

                 ## database type: MYSQL, PGSQL, DB_BERKELEY, or DBTEXT,

 by default none is loaded

                 # DBENGINE=DB_BERKELEY

@@ -209,11 +209,11 @@ by default none is loaded

                 METADATA_LOGFLAGS

                 0

-   Execute openserdbctl - There are three (3) groups of tables you

+   Execute kamdbctl - There are three (3) groups of tables you

    may need depending on your situation.

-                openserdbctl create             (required)

-                openserdbctl presence           (optional)

-                openserdbctl extra              (optional)

+                kamdbctl create             (required)

+                kamdbctl presence           (optional)

+                kamdbctl extra              (optional)

    Modify the OpenSER configuration file to use db_berkeley

    module. The database URL for modules must be the path to the

@@ -248,7 +248,7 @@ by default none is loaded

 1.7. Database Schema and Metadata

-   All Berkeley DB tables are created via the openserdbctl script.

+   All Berkeley DB tables are created via the kamdbctl script.

    This section provides details as to the content and format of

    the DB file upon creation.

@@ -396,28 +396,28 @@ r) last_name(str) email_address(str) datetime_created(datetime) timezone

    and syslog the value should be set to 1+16=17. Or if you do not

    want to journal at all, set this to 0.

-1.12. DB Maintaince Script : openserdbctl

+1.12. DB Maintaince Script : kamdbctl

-   Use the openserdbctl script for maintaining OpenSER Berkeley DB

+   Use the kamdbctl script for maintaining OpenSER Berkeley DB

    tables. This script assumes you have DBENGINE and DB_PATH setup

-   correctly in openserctlrc. Note Unsupported commands are-

+   correctly in kamctlrc. Note Unsupported commands are-

    backup, restore, migrate, copy, serweb.

-   Example 1.9. openserdbctl

-usage: openserdbctl create

-       openserdbctl presence

-       openserdbctl extra

-       openserdbctl drop

-       openserdbctl reinit

-       openserdbctl bdb list         (lists the underlying db files in D

+   Example 1.9. kamdbctl

+usage: kamdbctl create

+       kamdbctl presence

+       kamdbctl extra

+       kamdbctl drop

+       kamdbctl reinit

+       kamdbctl bdb list         (lists the underlying db files in D

 B_PATH)

-       openserdbctl bdb cat       db (prints the contents of db file to

+       kamdbctl bdb cat       db (prints the contents of db file to

 STDOUT in plain-text)

-       openserdbctl bdb swap      db (installs db.new by db -> db.old; d

+       kamdbctl bdb swap      db (installs db.new by db -> db.old; d

 b.new -> db)

-       openserdbctl bdb append    db datafile (appends data to a new ins

+       kamdbctl bdb append    db datafile (appends data to a new ins

 tance of db; output DB_PATH/db.new)

-       openserdbctl bdb newappend db datafile (appends data to a new ins

+       kamdbctl bdb newappend db datafile (appends data to a new ins

 tance of db; output DB_PATH/db.new)

 1.13. DB Recovery : bdb_recover

@@ -550,11 +550,11 @@ void bdblib_log(int op, table_p _tp, char* _msg, int len)

  * files (db) that we require.

  * 

  * There is one db file per openser table (eg. acc), and they should exist

- * in your DB_PATH (refer to openserctlrc) directory.

+ * in your DB_PATH (refer to kamctlrc) directory.

  *

  * This function does _not_ create the underlying binary db tables.

  * Creating the tables MUST be manually performed before 

- * openser startup by 'openserdbctl create'

+ * openser startup by 'kamdbctl create'

  *

  * Function returns NULL on error, which will cause openser to exit.

  *

@@ -145,7 +145,7 @@ modparam("db_berkeley", "journal_roll_interval", 3600)

 		<para>Parameters: <emphasis>tablename (or db_path); to reload a particular table 

 		provide the tablename as the arguement (eg subscriber); to reload all tables provide the db_path to

-		the db files. The path can be found in openserctlrc DB_PATH variable. 

+		the db files. The path can be found in kamctlrc DB_PATH variable. 

 		</emphasis></para>

 	</section>

 	</section>

@@ -192,20 +192,20 @@ modparam("db_berkeley", "journal_roll_interval", 3600)

 		as root user of the main directory. This will install the binaries 

 		in /usr/local/sbin/.

 		If this was successful, openser control engine files should now 

-		be installed as /usr/local/sbin/openserdbctl.

+		be installed as /usr/local/sbin/kamdbctl.

 		</para>

 		<para>

 		Decide where (on the filesystem) you want to install the Berkeley DB files.

 		For instance, '/usr/local/etc/openser/db_berkeley' directory.

-		Make note of this directory as we need to add this path to the openserctlrc file.

+		Make note of this directory as we need to add this path to the kamctlrc file.

 		Note: OpenSER will not startup without these DB files.

 		</para>

 		<para>

-		Edit openserctlrc - There are two parameters in this file that should be 

+		Edit kamctlrc - There are two parameters in this file that should be 

 		configured before openserctrdb script can work properly: DBENGINE and DB_PATH.

-		Edit file: '/usr/local/etc/openser/openserctlrc'

+		Edit file: '/usr/local/etc/openser/kamctlrc'

 		</para>

 	        <programlisting  format="linespecific">

 		## database type: MYSQL, PGSQL, DB_BERKELEY, or DBTEXT, by default none is loaded

@@ -234,13 +234,13 @@ modparam("db_berkeley", "journal_roll_interval", 3600)

 		<para>

-		Execute openserdbctl - There are three (3) groups of tables you may need depending

+		Execute kamdbctl - There are three (3) groups of tables you may need depending

 		on your situation.

 		</para>

 	        <programlisting  format="linespecific">

-		openserdbctl create   		(required)

-		openserdbctl presence 		(optional)

-		openserdbctl extra    		(optional)

+		kamdbctl create   		(required)

+		kamdbctl presence 		(optional)

+		kamdbctl extra    		(optional)

 		</programlisting>

 		<para>

@@ -284,7 +284,7 @@ modparam("db_berkeley", "journal_roll_interval", 3600)

 	<title>Database Schema and Metadata</title>

 	<para>

-	All Berkeley DB tables are created via the openserdbctl script. 

+	All Berkeley DB tables are created via the kamdbctl script. 

 	This section provides details as to the content and 

 	format of the DB file upon creation.

 	</para>

@@ -488,25 +488,25 @@ username(str) domain(str) password(str) ha1(str) ha1b(str) first_name(str) last_

 	</section>

 	<section>

-	<title>DB Maintaince Script : openserdbctl </title>

+	<title>DB Maintaince Script : kamdbctl </title>

 	<para>

-	Use the openserdbctl script for maintaining OpenSER Berkeley DB tables.

-	This script assumes you have DBENGINE and DB_PATH setup correctly in openserctlrc.

+	Use the kamdbctl script for maintaining OpenSER Berkeley DB tables.

+	This script assumes you have DBENGINE and DB_PATH setup correctly in kamctlrc.

 	Note Unsupported commands are- backup, restore, migrate, copy, serweb.

 	<example>

-	<title>openserdbctl</title>

+	<title>kamdbctl</title>

 	<programlisting>

-usage: openserdbctl create   

-       openserdbctl presence 

-       openserdbctl extra    

-       openserdbctl drop     

-       openserdbctl reinit   

-       openserdbctl bdb list         (lists the underlying db files in DB_PATH)

-       openserdbctl bdb cat       db (prints the contents of db file to STDOUT in plain-text)

-       openserdbctl bdb swap      db (installs db.new by db -> db.old; db.new -> db)

-       openserdbctl bdb append    db datafile (appends data to a new instance of db; output DB_PATH/db.new)

-       openserdbctl bdb newappend db datafile (appends data to a new instance of db; output DB_PATH/db.new)

+usage: kamdbctl create   

+       kamdbctl presence 

+       kamdbctl extra    

+       kamdbctl drop     

+       kamdbctl reinit   

+       kamdbctl bdb list         (lists the underlying db files in DB_PATH)

+       kamdbctl bdb cat       db (prints the contents of db file to STDOUT in plain-text)

+       kamdbctl bdb swap      db (installs db.new by db -> db.old; db.new -> db)

+       kamdbctl bdb append    db datafile (appends data to a new instance of db; output DB_PATH/db.new)

+       kamdbctl bdb newappend db datafile (appends data to a new instance of db; output DB_PATH/db.new)

 	</programlisting>

 	</example>

 	</para>

@@ -110,7 +110,7 @@ mv acc_4.log acc_3.log.20050605

        data into the renamed files.

      * Send Kamailio the MI command to close and reopen the

        renamed files. For example, using FIFO:

-openserctl fifo flat_rotate

+kamctl fifo flat_rotate

        This will force Kamailio to close the renamed files and

        open new ones with original names, such as acc_1.log. New

@@ -88,7 +88,7 @@ mv acc_4.log acc_3.log.20050605

 			Send &openser; the MI command to close and reopen the

 			renamed files. For example, using FIFO:

 			<screen>

-openserctl fifo flat_rotate

+kamctl fifo flat_rotate

 			</screen>

 			This will force &openser; to close the renamed files and open

 			new ones with original names, such as

@@ -128,7 +128,7 @@ modparam("db_oracle", "reconnect", 0.5)

 1.6. Utility openser_orasel

-   For working with openserctl script, should be able to print the

+   For working with kamctl script, should be able to print the

    'query' results to the terminal in a user-readable form. The

    standard command-line Oracle client (sqlplus) is not quite

    suitable for this, as it cannot align row width to real

@@ -136,7 +136,7 @@ modparam("db_oracle", "reconnect", 0.5)

 	<section>

 	<title>Utility openser_orasel</title>

 		<para>

-		For working with openserctl script, should be able to print the 'query' 

+		For working with kamctl script, should be able to print the 'query' 

 		results to the terminal in a user-readable form. The standard command-line 

 		Oracle client (sqlplus) is not quite suitable for this, as it cannot align 

 		row width to real (received) data's (it always prints a cell width as 

@@ -445,7 +445,7 @@ int init_ds_db(void)

 	} else if (_ds_table_version != DS_TABLE_VERSION

 			&& _ds_table_version != DS_TABLE_VERSION2) {

 		LM_ERR("invalid table version (found %d , required %d or %d)\n"

-			"(use openserdbctl reinit)\n",

+			"(use kamdbctl reinit)\n",

 			_ds_table_version, DS_TABLE_VERSION, DS_TABLE_VERSION2 );

 		return -1;

 	}

@@ -149,8 +149,8 @@ if(is_gflag("4"))

    Example 1.5. set_gflag usage

 ...

-$ openserctl fifo set_gflag 1

-$ openserctl fifo set_gflag 0x3

+$ kamctl fifo set_gflag 1

+$ kamctl fifo set_gflag 0x3

 ...

 1.5.2. reset_gflag

@@ -161,8 +161,8 @@ $ openserctl fifo set_gflag 0x3

    Example 1.6.  reset_gflag usage

 ...

-$ openserctl fifo reset_gflag 1

-$ openserctl fifo reset_gflag 0x3

+$ kamctl fifo reset_gflag 1

+$ kamctl fifo reset_gflag 0x3

 ...

 1.5.3. is_gflag

@@ -174,19 +174,19 @@ $ openserctl fifo reset_gflag 0x3

    Example 1.7. is_gflag usage

 ...

-$ openserctl fifo set_gflag 1024

-$ openserctl fifo is_gflag 1024

+$ kamctl fifo set_gflag 1024

+$ kamctl fifo is_gflag 1024

 TRUE

-$ openserctl fifo is_gflag 1025

+$ kamctl fifo is_gflag 1025

 TRUE

-$ openserctl fifo is_gflag 1023

+$ kamctl fifo is_gflag 1023

 FALSE

-$ openserctl fifo set_gflag 0x10

-$ openserctl fifo is_gflag 1023

+$ kamctl fifo set_gflag 0x10

+$ kamctl fifo is_gflag 1023

 TRUE

-$ openserctl fifo is_gflag 1007

+$ kamctl fifo is_gflag 1007

 FALSE

-$ openserctl fifo is_gflag 16

+$ kamctl fifo is_gflag 16

 TRUE

 ...

@@ -197,7 +197,7 @@ TRUE

    Example 1.8.  get_gflags usage

 ...

-$ openserctl fifo get_gflags

+$ kamctl fifo get_gflags

 0x3039

 12345

 ...

@@ -152,8 +152,8 @@ if(is_gflag("4"))

 			<title><function moreinfo="none">set_gflag</function> usage</title>

 			<programlisting format="linespecific">

 ...

-$ openserctl fifo set_gflag 1

-$ openserctl fifo set_gflag 0x3

+$ kamctl fifo set_gflag 1

+$ kamctl fifo set_gflag 0x3

 ...

 </programlisting>

 			</example>

@@ -172,8 +172,8 @@ $ openserctl fifo set_gflag 0x3

 				<function moreinfo="none">reset_gflag</function> usage</title>

 			<programlisting format="linespecific">

 ...

-$ openserctl fifo reset_gflag 1

-$ openserctl fifo reset_gflag 0x3

+$ kamctl fifo reset_gflag 1

+$ kamctl fifo reset_gflag 0x3

 ...

 </programlisting>

 			</example>

@@ -191,19 +191,19 @@ $ openserctl fifo reset_gflag 0x3

 			<title><function moreinfo="none">is_gflag</function> usage</title>

 			<programlisting format="linespecific">

 ...

-$ openserctl fifo set_gflag 1024

-$ openserctl fifo is_gflag 1024

+$ kamctl fifo set_gflag 1024

+$ kamctl fifo is_gflag 1024

 TRUE

-$ openserctl fifo is_gflag 1025

+$ kamctl fifo is_gflag 1025

 TRUE

-$ openserctl fifo is_gflag 1023

+$ kamctl fifo is_gflag 1023

 FALSE

-$ openserctl fifo set_gflag 0x10

-$ openserctl fifo is_gflag 1023

+$ kamctl fifo set_gflag 0x10

+$ kamctl fifo is_gflag 1023

 TRUE

-$ openserctl fifo is_gflag 1007

+$ kamctl fifo is_gflag 1007

 FALSE

-$ openserctl fifo is_gflag 16

+$ kamctl fifo is_gflag 16

 TRUE

 ...

 </programlisting>

@@ -220,7 +220,7 @@ TRUE

 				<function moreinfo="none">get_gflags</function> usage</title>

 			<programlisting format="linespecific">

 ...

-$ openserctl fifo get_gflags

+$ kamctl fifo get_gflags

 0x3039

 12345

 ...

@@ -593,7 +593,7 @@ start_recording();

    Example 1.23. nh_enable_ping usage

 ...

-$ openserctl fifo nh_enable_ping 1

+$ kamctl fifo nh_enable_ping 1

 ...

 1.7.2. nh_enable_rtpp

@@ -611,7 +611,7 @@ $ openserctl fifo nh_enable_ping 1

    Example 1.24.  nh_enable_rtpp usage

 ...

-$ openserctl fifo nh_enable_rtpp udp:192.168.2.133:8081 0

+$ kamctl fifo nh_enable_rtpp udp:192.168.2.133:8081 0

 ...

 1.7.3. nh_show_rtpp

@@ -623,7 +623,7 @@ $ openserctl fifo nh_enable_rtpp udp:192.168.2.133:8081 0

    Example 1.25.  nh_show_rtpp usage

 ...

-$ openserctl fifo nh_show_rtpp

+$ kamctl fifo nh_show_rtpp

 ...

 Chapter 2. Frequently Asked Questions

@@ -805,7 +805,7 @@ start_recording();

 			<title><function moreinfo="none">nh_enable_ping</function> usage</title>

 			<programlisting format="linespecific">

 ...

-$ openserctl fifo nh_enable_ping 1

+$ kamctl fifo nh_enable_ping 1

 ...

 			</programlisting>

 			</example>

@@ -833,7 +833,7 @@ $ openserctl fifo nh_enable_ping 1

 			<function moreinfo="none">nh_enable_rtpp</function> usage</title>

 			<programlisting format="linespecific">

 ...

-$ openserctl fifo nh_enable_rtpp udp:192.168.2.133:8081 0

+$ kamctl fifo nh_enable_rtpp udp:192.168.2.133:8081 0

 ...

 			</programlisting>

 			</example>

@@ -853,7 +853,7 @@ $ openserctl fifo nh_enable_rtpp udp:192.168.2.133:8081 0

 				<function moreinfo="none">nh_show_rtpp</function> usage</title>

 			<programlisting format="linespecific">

 ...

-$ openserctl fifo nh_show_rtpp 

+$ kamctl fifo nh_show_rtpp 

 ...

 			</programlisting>

 			</example>

@@ -79,9 +79,9 @@ Chapter 1. Admin Guide

    The tracing can be turned on/off using fifo commad.

-   openserctl fifo sip_trace on

+   kamctl fifo sip_trace on

-   openserctl fifo sip_trace off

+   kamctl fifo sip_trace off

 1.2. Dependencies

@@ -33,10 +33,10 @@

 	The tracing can be turned on/off using fifo commad.

 	</para>

 	<para>

-	openserctl fifo sip_trace on

+	kamctl fifo sip_trace on

 	</para>

 	<para>

-	openserctl fifo sip_trace off

+	kamctl fifo sip_trace off

 	</para>

 	</section>

 	<section>

@@ -575,7 +575,7 @@ dules/snmpstats.so>:

     LD_LIBRARY_PATH=/path/noted/in/step/one/above

    For example, on my system I ran:

-    LD_LIBRARY_PATH=/usr/local/lib openserctl start

+    LD_LIBRARY_PATH=/usr/local/lib kamctl start

    2.6.

@@ -198,7 +198,7 @@

 		</para>

 		<programlisting format="linespecific">

-    LD_LIBRARY_PATH=/usr/local/lib openserctl start

+    LD_LIBRARY_PATH=/usr/local/lib kamctl start

 		</programlisting>

 	    </answer>

@@ -184,7 +184,7 @@ if (!check_blacklist("global_blacklist")))

    Example 1.6. reload_blacklists usage

 ...

-openserctl fifo reload_blacklist

+kamctl fifo reload_blacklist

 ...

 1.6. Installation and Running

@@ -185,7 +185,7 @@ if (!check_blacklist("global_blacklist")))

 		<title><function>reload_blacklists</function> usage</title>

 		<programlisting format="linespecific">

 ...

-openserctl fifo reload_blacklist

+kamctl fifo reload_blacklist

 ...

 		</programlisting>

 	    </example>

@@ -76,7 +76,7 @@ static int mi_child_init(void);

 static void mod_destroy(void);

 /* --- fifo functions */

-struct mi_root * mi_reload_blacklist(struct mi_root* cmd, void* param);  /* usage: openserctl fifo reload_blacklist */

+struct mi_root * mi_reload_blacklist(struct mi_root* cmd, void* param);  /* usage: kamctl fifo reload_blacklist */

 static cmd_export_t cmds[]={