1TTSERVER(1)                      Tokyo Tyrant                      TTSERVER(1)
2
3
4

NAME

6       ttserver - the server of Tokyo Tyrant
7
8

DESCRIPTION

10       The  command  `ttserver'  runs the server managing a database instance.
11       Because the database is treated by the abstract API of  Tokyo  Cabinet,
12       you  can choose the scheme on start-up of the server.  Supported schema
13       are on-memory hash database, on-memory tree  database,  hash  database,
14       and  B+  tree  database.  This command is used in the following format.
15       `dbname' specifies the database name.  If it is omitted, on-memory hash
16       database is specified.
17
18              ttserver  [-host  name]  [-port  num]  [-thnum  num] [-tout num]
19              [-dmn] [-pid path] [-kl]  [-log  path]  [-ld|-le]  [-ulog  path]
20              [-ulim  num]  [-uas] [-sid num] [-mhost name] [-mport num] [-rts
21              path] [-rcc] [-skel name] [-mul num] [-ext  path]  [-extpc  name
22              period] [-mask expr] [-unmask expr] [dbname]
23
24       Options feature the following.
25
26              -host name : specify the host name or the address of the server.
27              By default, every network address is bound.
28              -port num : specify the port number.  By default, it is 1978.
29              -thnum num : specify the number of worker threads.  By  default,
30              it is 8.
31              -tout  num : specify the timeout of each session in seconds.  By
32              default, no timeout is specified.
33              -dmn : work as a daemon process.
34              -pid path : output the process ID into the file.
35              -kl : kill the existing  process  if  the  process  ID  file  is
36              detected.
37              -log path : output log messages into the file.
38              -ld : log debug messages also.
39              -le : log error messages only.
40              -ulog path : specify the update log directory.
41              -ulim num : specify the limit size of each update log file.
42              -uas : use asynchronous I/O for the update log.
43              -sid num : specify the server ID.
44              -mhost  name  :  specify the host name of the replication master
45              server.
46              -mport num : specify the port number of the  replication  master
47              server.
48              -rts path : specify the replication time stamp file.
49              -rcc : check consistency of replication.
50              -skel name : specify the name of the skeleton database library.
51              -mul  num : specify the division number of the multiple database
52              mechanism.
53              -ext path : specify the script language extension file.
54              -extpc name period : specify the function name and  the  calling
55              period of a periodic command.
56              -mask expr : specify the names of forbidden commands.
57              -unmask expr : specify the names of allowed commands.
58
59       To  terminate  the  server  normally,  send  SIGINT  or  SIGTERM to the
60       process.  It is okay to press Ctrl-C on the controlling  terminal.   To
61       restart  the server, send SIGHUP to the process.  If the port number is
62       not more than 0, UNIX domain socket is used and the path of the  socket
63       file  is  specified  by  the host parameter.  This command returns 0 on
64       success, another on failure.
65
66       The naming convention of the database is specified by the abstract  API
67       of  Tokyo Cabinet.  If the name is "*", the database will be an on-mem‐
68       ory hash database.  If it is "+", the database  will  be  an  on-memory
69       tree  database.   If  its suffix is ".tch", the database will be a hash
70       database.  If its suffix is ".tcb", the database  will  be  a  B+  tree
71       database.  If its suffix is ".tcf", the database will be a fixed-length
72       database.  If its suffix is ".tct", the database will be a table  data‐
73       base.  Otherwise, this function fails.  Tuning parameters can trail the
74       name, separated by "#".  Each parameter is composed of the name and the
75       value,  separated  by  "=".   On-memory  hash database supports "bnum",
76       "capnum", and "capsiz".  On-memory tree database supports "capnum"  and
77       "capsiz".   Hash  database  supports  "mode",  "bnum",  "apow", "fpow",
78       "opts", "rcnum",  and  "xmsiz".   B+  tree  database  supports  "mode",
79       "lmemb", "nmemb", "bnum", "apow", "fpow", "opts", "lcnum", "ncnum", and
80       "xmsiz".  Fixed-length database supports "mode", "width", and "limsiz".
81       Table   database  supports  "mode",  "bnum",  "apow",  "fpow",  "opts",
82       "rcnum", "lcnum", "ncnum", "xmsiz", and "idx".   The  tuning  parameter
83       "capnum"  specifies the capacity number of records.  "capsiz" specifies
84       the capacity size of using memory.  Records spilled  the  capacity  are
85       removed by the storing order.  "mode" can contain "w" of writer, "r" of
86       reader, "c" of creating, "t" of truncating, "e" of no locking, and  "f"
87       of  non-blocking  lock.   The default mode is relevant to "wc".  "opts"
88       can contains "l" of large option, "d" of Deflate option, "b"  of  BZIP2
89       option,  and "t" of TCBS option.  "idx" specifies the column name of an
90       index  and  its  type   separated   by   ":".    For   example,   "cas‐
91       ket.tch#bnum=1000000#opts=ld"  means that the name of the database file
92       is "casket.tch", and the bucket number is 1000000, and the options  are
93       large and Deflate.
94
95       The  command  mask  expression  is a list of command names separated by
96       ",".  For example, "out,vanish,copy" means a set  of  "out",  "vanish",
97       and "copy".  Commands of the memcached compatible protocol and the HTTP
98       compatible protocol are also forbidden or allowed, related by the  mask
99       of each original command.  Moreover, there are meta expressions.  "all"
100       means all commands.  "allorg" means all commands of the original binary
101       protocol.   "allmc" means all commands of the memcached compatible pro‐
102       tocol.  "allhttp" means all commands of the HTTP  compatible  protocol.
103       "allread"  is  the  abbreviation  of `get', `mget', `vsiz', `iterinit',
104       `iternext', `fwmkeys', `rnum', `size', and `stat'.  "allwrite"  is  the
105       abbreviation  of  `put', `putkeep', `putcat', `putshl', `putnr', `out',
106       `addint', `adddouble', `vanish', and `misc'.  "allmanage" is the abbre‐
107       viation of `sync', `optimize', `copy', `restore', and `setmst'.  "repl"
108       means replication as master.  "slave" means replication as slave.
109
110

SEE ALSO

112       ttultest(1),   ttulmgr(1),   tcrtest(1),    tcrmttest(1),    tcrmgr(1),
113       ttutil(3), ttulog(3), tcrdb(3), ttservctl(8)
114
115
116
117Man Page                          2010-01-20                       TTSERVER(1)
Impressum