File: trafficserver.default

package info (click to toggle)
trafficserver 6.2.0-1~bpo8%2B1
  • links: PTS, VCS
  • area: main
  • in suites: jessie-backports
  • size: 45,456 kB
  • sloc: cpp: 271,894; ansic: 80,740; sh: 6,032; makefile: 3,364; python: 2,135; perl: 2,040; java: 277; lex: 128; sql: 94; yacc: 68; sed: 8
file content (64 lines) | stat: -rw-r--r-- 2,094 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
## Defaults for trafficserver initscript
## sourced by /etc/init.d/trafficserver
## installed at /etc/default/trafficserver by the maintainer scripts

##
## This is a POSIX shell fragment
##

## Variable: RUNDIR
## Default: /var/run/trafficserver
## Description: Set this to the directory where runtime data is stored. The
##              default value should work fine for almost all users.
# RUNDIR=/var/run/trafficserver

## Variable: TC_START
## Default: no
## Description: Set to "yes" if you want the init script to start the
##              `traffic_cop' binary. Usually this is what most users want
TC_START=yes

## Variable: TC_DAEMON_ARGS
## Default: (empty)
## Description: Set here command line arguments the init script shall pass
##              through `traffic_cop' upon startup.
# TC_DAEMON_ARGS=""

## Variable: TC_PIDFILE
## Default: $RUNDIR/cop.lock
## Description: Set this to a (writable) path where the PID file of the
##              `traffic_cop' script should be stored. Most likely you don't
##              need to change this value.
# TC_PIDFILE=$RUNDIR/cop.lock


##
## NOTICE:
##        Typically you do not want to configure anything below. Note, generally Traffic
##        Server is started through `traffic_cop' which is a watchdog to control any local
##        Traffic Server instances. It starts both, traffic_manager and traffic_server, as
##        does it monitor these processes. While it is generally not advised, you can
##        choose to manage both processes yourself. In such cases do not set TC_START to
##        "yes" and enable any service you want below.
##
##        Choose either alternative, but do not mix up both.


## Configuration for `traffic_manager'.
## Meaning of variables is analogous to traffic_cop above, but for the
## `traffic_manager' binary.

# TM_START=no
# TM_DAEMON_ARGS=""
# TM_PIDFILE=$RUNDIR/manager.lock



## Configuration for `traffic_server'.
## Meaning of variables is analogous to traffic_cop above, but for the
## `traffic_server' binary.

# TS_START=no
# TS_DAEMON_ARGS=""
# TS_PIDFILE=$RUNDIR/server.lock