blob: d842627b2bbae1ea67eeae13e33e0bd3aca881b1 (
plain)
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
|
<!--
$FML: filename.sgml,v 1.2 2003/08/03 05:28:49 fukachan Exp $
$jaFML: filename.sgml,v 1.3 2003/04/15 14:51:41 fukachan Exp $
-->
<chapter id="filename">
<title>
[Caution] File Names
</title>
<para>
References: fml-devel 205
</para>
<sect1 id="filename.basic">
<title>
Filename Structure
</title>
<para>
The fundamental syntax is
<screen>
FILENAME-ROLE
</screen>
.
For example, fml uses the following syntax for address lists.
<screen>
recipients-ROLE
members-ROLE
</screen>
</para>
<para>
Other than address lists, fml uses similar manner for other type of
files. For example,
<screen>
passwd-admin
passwd-moderator
passwd-cgiadmin
</screen>
for several password files.
</para>
</sect1>
<sect1>
<title>
Case Study: Address List
</title>
<para>
<screen>
primary_recipient_maps = recipients
# add actives for backward compatibility
recipient_maps = recipients
actives
</screen>
</para>
</sect1>
<sect1>
<title>
Case Study: List Of Remote Administrators
</title>
<para>
<screen>
recipients-admin
members-admin
</screen>
</para>
</sect1>
<sect1>
<title>
Case Study: List Of Moderators
</title>
<para>
<screen>
recipients-moderator
members-moderator
</screen>
</para>
</sect1>
<sect1>
<title>
Case Study: Remote Administrator Password Files
</title>
<para>
<screen>
etc/passwd-admin
</screen>
</para>
<warning>
<para>
etc/passwd, lack of role name, was used in the case of &fml4;.
</para>
</warning>
</sect1>
</chapter>
<!--
[HISTORY]
imported from
01_RFC_FILENAME.txt,v 1.2 2002/08/21 15:30:25 fukachan Exp
-->
|
