File: trafficserver.default

package info (click to toggle)
trafficserver 9.2.5%2Bds-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 53,008 kB
  • sloc: cpp: 345,484; ansic: 31,134; python: 24,200; sh: 7,271; makefile: 3,045; perl: 2,261; java: 277; pascal: 119; sql: 94; xml: 2
file content (41 lines) | stat: -rw-r--r-- 1,413 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
## 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: /run/trafficserver
## Description: Set this to the directory where runtime data is stored. The
##              default value should work fine for almost all users.
# RUNDIR=/run/trafficserver


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

TM_START=yes
# TM_DAEMON_ARGS=""
# TM_PIDFILE=$RUNDIR/manager.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_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