-
Notifications
You must be signed in to change notification settings - Fork 20
/
Copy pathsynctool.conf.example
186 lines (151 loc) · 5.19 KB
/
synctool.conf.example
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
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
#
# synctool.conf
#
# This is an example file; adjust your synctool.conf as needed
# commented parameters resemble built-in defaults
# specify groups and nodes
# by default, synctool will run on these nodes
# You can specify a certain group or a list of groups/nodes
# 'none' will result in synctool not running at all
# This setting can be overridden by passing the nodes on the command-line
#default_nodeset all
# designate node0 as master node
# the fqdn (fully qualified domain name) is given as argument
master node0.mycluster.org
# slave nodes get a full copy of the synctool repository
#slave node8 node9
# compound groups may be specified like this
group wn workernode batch
group test wn
group g1 batch test wn
# list all nodes and their groups
# the nodename is a logical name known only to synctool
# "ipaddress:" specifies the IP address where synctool connects to
#
# Optionally, 'rsync:no' may be given to keep synctool from rsync-ing
# the repository to that node. This is only useful when the node has access
# to the repository via shared storage (like an NFS share)
# managing the masternode also with synctool is generally not a great idea
#node node0 master
node node1 fs sched aix ipaddress:node1-mgmt
node node2 login debian ipaddress:node2-mgmt
node node3 wn debian ipaddress:node3-mgmt
node node4 wn debian ipaddress:node4-mgmt rsync:no
node node5 wn centos ipaddress:node5-mgmt rsync:no
node node6 wn centos ipaddress:node6-mgmt
node node7 wn centos ipaddress:node7-mgmt
node node8 test sunos ipaddress:node8-mgmt
node node9 batch sunos ipaddress:node9-mgmt
# node10 to node25 are all the same
node node[10-25] wn debian
# other examples of ranges of nodes
node node[001-100] wn debian ipaddress:node[001]-mgmt
node node[101-200] wn debian ipaddress:192.168.1.[20]
# ignore one or more nodes
ignore_node node0 node9
# ignore a number of groups
ignore_group test test2
# ignore all files beginning with a dot (like .profile, .bashrc, ...)
#ignore_dotfiles no
# ignore all directories beginning with a dot (like .git, .svn, ...)
#ignore_dotdirs no
# ignore certain files/directories
ignore .svn
ignore .gitignore
ignore .*.swp
#tempdir /tmp/synctool
# ssh multiplexing persistance timeout
# you may set this to 'yes' to keep it around indefinitely
# or to 'none' to not use it at all
#ssh_control_persist 1h
# all files in the repository must have a group extension
#require_extension yes
# make backup copies named *.saved
#backup_copies yes
# log to syslog
#syslogging yes
# copy file last modified time from repository
#sync_times no
# configure external commands that synctool uses
#diff_cmd diff -u
#ping_cmd fping -t 500
#ping_cmd ping -q -c 1 -w 1
# synctool depends on ssh, but this command is configurable
# so that you can do things like:
# ssh -T -n
# or ssh -c arcfour
#
#ssh_cmd ssh -o ConnectTimeout=10 -x -q
# synctool depends on rsync, but this command is configurable
# so that you can do things like:
# rsync_cmd rsync -ar --dry-run -vv
# or rsync_cmd rsync -ar --delete --delete-excluded --numeric-ids
#
# synctool automatically appends option: -e ssh_cmd
# synctool automatically appends another option:
# --filter=/tmp/synctool/synctool-tempfile
#
#rsync_cmd rsync -ar --delete --delete-excluded -q
#synctool_cmd $SYNCTOOL/bin/synctool-client
#pkg_cmd $SYNCTOOL/bin/synctool-client-pkg
# Force the package manager for synctool-pkg / dsh-pkg to use
# If you don't configure one, synctool-pkg will detect one
# (this is usually OK)
#
# If you do not want to detect it, choose one of the supported
# package managers.
#
# Note: Multi-platform setups
# It makes no sense to force a single package manager onto a heterogeneous
# cluster. If you run a multi-platform setup and need to force
# the package_manager, solve it with a local include, like:
# include /etc/synctool_local.conf
# You can still override this setting from the command-line when invoking
# synctool-pkg.
#
#package_manager apk
#package_manager apt-get
#package_manager brew
#package_manager bsdpkg
#package_manager dnf
#package_manager pacman
#package_manager pkg
#package_manager yum
#package_manager zypper
# max amount of parallel processes that synctool uses on the master node
#num_proc 16
# display full paths or just '$overlay/...'
#full_path no
# show terse output with shortened paths?
# shortened paths look like '//overlay/all/.../sshd_config._all'
#terse no
# colorize output? Note that colors only work for 'terse' output!
#colorize yes
# colorize the full line of output (yes) or just one word (no) ?
#colorize_full_line no
# use bright/bold attribute?
#colorize_bright yes
# specify colors
# valid values are: black, darkgray, red, green, yellow, blue,
# magenta, cyan, white, bold, default
# 'default' means that no color is used
#color_info default
#color_warn magenta
#color_error red
#color_fail red
#color_sync default
#color_link cyan
#color_mkdir blue
#color_rm yellow
#color_chown cyan
#color_chmod cyan
#color_exec green
#color_upload magenta
#color_new default
#color_type magenta
#color_dryrun default
#color_fixing default
#color_ok default
# include a local synctool config file on the target node
#include /etc/synctool_local.conf
# EOB