This file is indexed.

/usr/share/doc/slony1-2-doc/adminguide/mkservice.html is in slony1-2-doc 2.2.5-2.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  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
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>mkservice </TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:slony1-general@lists.slony.info"><LINK
REL="HOME"
TITLE="Slony-I 2.2.5 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="Additional Utilities"
HREF="additionalutils.html"><LINK
REL="PREVIOUS"
TITLE=" Log Files"
HREF="logrotation.html"><LINK
REL="NEXT"
TITLE=" Slony-I Test Suites "
HREF="testing.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"></HEAD
><BODY
CLASS="SECT1"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="5"
ALIGN="center"
VALIGN="bottom"
><SPAN
CLASS="PRODUCTNAME"
>Slony-I</SPAN
> 2.2.5 Documentation</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="logrotation.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="additionalutils.html"
>Fast Backward</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
>Chapter 6. Additional Utilities</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="additionalutils.html"
>Fast Forward</A
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="testing.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="MKSERVICE"
>6.5. mkservice</A
></H1
><A
NAME="AEN4815"
></A
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN4817"
>6.5.1. slon-mkservice.sh</A
></H2
><P
> Create a slon service directory for use with svscan from
daemontools.  This uses multilog in a pretty basic way, which seems to
be standard for daemontools / multilog setups. If you want clever
logging, see logrep below. Currently this script has very limited
error handling capabilities.</P
><P
> For non-interactive use, set the following environment
variables.  <TT
CLASS="ENVAR"
>BASEDIR</TT
> <TT
CLASS="ENVAR"
>SYSUSR</TT
>
<TT
CLASS="ENVAR"
>PASSFILE</TT
> <TT
CLASS="ENVAR"
>DBUSER</TT
> <TT
CLASS="ENVAR"
>HOST</TT
>
<TT
CLASS="ENVAR"
>PORT</TT
> <TT
CLASS="ENVAR"
>DATABASE</TT
> <TT
CLASS="ENVAR"
>CLUSTER</TT
>
<TT
CLASS="ENVAR"
>SLON_BINARY</TT
> If any of the above are not set, the script
asks for configuration information interactively.</P
><P
></P
><UL
><LI
><P
><TT
CLASS="ENVAR"
>BASEDIR</TT
> where you want the service directory structure for the slon
to be created. This should <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>not</I
></SPAN
> be the <TT
CLASS="FILENAME"
>/var/service</TT
> directory.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>SYSUSR</TT
> the unix user under which the slon (and multilog) process should run.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>PASSFILE</TT
> location of the <TT
CLASS="FILENAME"
>.pgpass</TT
> file to be used. (default <TT
CLASS="FILENAME"
>~sysusr/.pgpass</TT
>)</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>DBUSER</TT
> the postgres user the slon should connect as (default slony)</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>HOST</TT
> what database server to connect to (default localhost)</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>PORT</TT
> what port to connect to (default 5432)</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>DATABASE</TT
> which database to connect to (default dbuser)</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>CLUSTER</TT
> the name of your Slony1 cluster? (default database)</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>SLON_BINARY</TT
> the full path name of the slon binary (default <TT
CLASS="COMMAND"
>which slon</TT
>)</P
></LI
></UL
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN4863"
>6.5.2. logrep-mkservice.sh</A
></H2
><A
NAME="AEN4865"
></A
><P
>This uses <TT
CLASS="COMMAND"
>tail -F</TT
> to pull data from log files allowing
you to use multilog filters (by setting the CRITERIA) to create
special purpose log files. The goal is to provide a way to monitor log
files in near realtime for <SPAN
CLASS="QUOTE"
>"interesting"</SPAN
> data without either
hacking up the initial log file or wasting CPU/IO by re-scanning the
same log repeatedly.</P
><P
>For non-interactive use, set the following environment
variables.  <TT
CLASS="ENVAR"
>BASEDIR</TT
> <TT
CLASS="ENVAR"
>SYSUSR</TT
> <TT
CLASS="ENVAR"
>SOURCE</TT
>
<TT
CLASS="ENVAR"
>EXTENSION</TT
> <TT
CLASS="ENVAR"
>CRITERIA</TT
> If any of the above are not set,
the script asks for configuration information interactively.</P
><P
></P
><UL
><LI
><P
><TT
CLASS="ENVAR"
>BASEDIR</TT
> where you want the service directory structure for the logrep
to be created. This should <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>not</I
></SPAN
> be the <TT
CLASS="FILENAME"
>/var/service</TT
> directory.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>SYSUSR</TT
> unix user under which the service should run.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>SOURCE</TT
> name of the service with the log you want to follow.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>EXTENSION</TT
> a tag to differentiate this logrep from others using the same source.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>CRITERIA</TT
> the multilog filter you want to use.</P
></LI
></UL
><P
> A trivial example of this would be to provide a log file of all slon
ERROR messages which could be used to trigger a nagios alarm.
<TT
CLASS="COMMAND"
>EXTENSION='ERRORS'</TT
>
<TT
CLASS="COMMAND"
>CRITERIA="'-*' '+* * ERROR*'"</TT
>
(Reset the monitor by rotating the log using <TT
CLASS="COMMAND"
>svc -a $svc_dir</TT
>)</P
><P
> A more interesting application is a subscription progress log.
<TT
CLASS="COMMAND"
>EXTENSION='COPY'</TT
>
<TT
CLASS="COMMAND"
>CRITERIA="'-*' '+* * ERROR*' '+* * WARN*' '+* * CONFIG enableSubscription*' '+* * DEBUG2 remoteWorkerThread_* prepare to copy table*' '+* * DEBUG2 remoteWorkerThread_* all tables for set * found on subscriber*' '+* * DEBUG2 remoteWorkerThread_* copy*' '+* * DEBUG2 remoteWorkerThread_* Begin COPY of table*' '+* * DEBUG2 remoteWorkerThread_* * bytes copied for table*' '+* * DEBUG2 remoteWorkerThread_* * seconds to*' '+* * DEBUG2 remoteWorkerThread_* set last_value of sequence*' '+* * DEBUG2 remoteWorkerThread_* copy_set*'"</TT
></P
><P
>If you have a subscription log then it's easy to determine if a given
slon is in the process of handling copies or other subscription activity.
If the log isn't empty, and doesn't end with a 
<TT
CLASS="COMMAND"
>"CONFIG enableSubscription: sub_set:1"</TT
>
(or whatever set number you've subscribed) then the slon is currently in
the middle of initial copies.</P
><P
> If you happen to be monitoring the mtime of your primary slony logs to 
determine if your slon has gone brain-dead, checking this is a good way
to avoid mistakenly clobbering it in the middle of a subscribe. As a bonus,
recall that since the the slons are running under svscan, you only need to
kill it (via the svc interface) and let svscan start it up again laster.
I've also found the COPY logs handy for following subscribe activity 
interactively.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="logrotation.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="testing.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Log Files</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="additionalutils.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><SPAN
CLASS="PRODUCTNAME"
>Slony-I</SPAN
> Test Suites</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>