/
daitss-config.example.yml
39 lines (35 loc) · 1.5 KB
/
daitss-config.example.yml
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
# This is an example of the DAITSS configuration file restricted to
# the data necessary to run the viruscheck service.
#
# You must set up your web server to set the environment variable
# DAITSS_CONFIG to point to a configuration file along these lines,
# though typically it will have sections for many services in addition
# to this one.
#
# Please don't use tabs in this file.
defaults:
# We normally name sections after the virtual hostname used by an
# applcation (this is so one physical host can run multiple services
# of the same kind). An application's configuration code typically
# checks the VIRTUAL_HOSTNAME environment variable to determine the
# appropriate section to load. Typically VIRTUAL_HOSTNAME is set in
# the same place that the DAITSS_CONFIG environment is set.
viruscheck.example.org:
log_syslog_facility: LOG_LOCAL0
log_filename: viruscheck.log
clamd: false
# viruscheck:log_syslog_facility
# -------------------------------
# If set, direct log information to this syslog facility (see
# /etc/syslog.conf). If neither log_filename nor log_syslog_facility
# are set, log to STDERR.
#
# viruscheck:log_filename
# -------------------------------
# If set, direct log information to this file. If neither log_filename
# nor log_syslog_facility are set, log to STDERR.
##
# viruscheck:clamd
# --------------------------
# Set this to true if clamd is installed and you wish to use it
# instead of invoking the stand-alone clam process for each file.