File: config.sample

package info (click to toggle)
post-faq 0.10-13
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 172 kB
  • ctags: 26
  • sloc: perl: 313; makefile: 43; sh: 26; awk: 7
file content (70 lines) | stat: -rw-r--r-- 3,028 bytes parent folder | download | duplicates (7)
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
# $Header: /afs/sipb.mit.edu/project/periodic-postings/post_faq/RCS/config.sample,v 1.1 1994/01/25 19:47:20 jik Exp $
# 
# Sample post_faq configuration file.
# 
# Copyright (c) 1994 Jonathan I. Kamens.  See the GNU Public License
# (any version) for terms of distribution.
# 
# Note that this entire introductory text is ignored by post_faq
# because its lines start with '#'.  Lines containing only whitespace
# are also ignored.

# The format of FAQ lines in the post_faq configuration file is as
# follows:
# 
#   idname file timestamp interval sigfile force parent
# 
# Fields are whitespace separated.  Empty fields are signified by a
# single period ('.').  The comment at the beginning of the parse_faq
# function in faqfile.pl documents each of the fields in detail, as
# does the post_faq man page, so all that information will not be
# repeated here.

# Here's an FAQ that has never been posted before, should be posted
# every thirty days, shouldn't have any signature file appended to it,
# and has no parent.
# 
# Note that the first time the FAQ is posted, the '.' in the timestamp
# field will be replaced with the timestamp of the time at which it
# was posted.

sample1  /home/joeruser/doc/sample1.txt  .  30  none  .  .

# Here's an FAQ which is similar to the one above, but which will
# posted whether it's due or not the next time post_faq is run.  After
# it's posted, the '1' in the force field will be replaced with '.'.

sample2  /home/joeruser/doc/sample2.txt  .  30  none  1  .

# Here's an FAQ which will be posted whether it's due or not every
# time post_faq is run, and which was last posted on January 25, 1994.

sample3  /home/joeruser/doc/sample3.txt  759522778  30  none  2  .

# Here's an FAQ which will never be posted, until it is unsuspended by
# changing the force field to something other than -1.

sample4  /home/joeruser/doc/sample4.txt  .  30  none  -1  .

# Here's an FAQ with a signature file which will be posted on the
# first Monday of every month, along with a child which will always be
# posted with it and never otherwise.
# 
# Some notes about parents and children:
# 
# * A child will be posted only when its parent is, and never
#   otherwise.  However, if its interval is different than its
#   parent's, or if its force field specifies that it should not be
#   posted, it might not be posted when its parent is.
# * A child must appear after its parent in the configuration file.
# 
# Note that post_faq will not put an "Expires" line in an FAQ being
# posted with cron-like intervals, unless -expire_search is specified
# on the command line (or expire_search is set to true in config.dat
# before installing post_faq).

sample5.p1  /home/joeruser/doc/sample5.p1  .  '($wday == 1) && ($mday <= 7)'  /home/joeruser/.signature  .  .
sample5.p2  /home/joeruser/doc/sample5.p1  .  '($wday == 1) && ($mday <= 7)'  /home/joeruser/.signature  .  sample5.p1

# If you think that this file should contain other examples, please
# let me know what you think needs to be added.