blob: 83c33898dfa7a0180f7456400f78a26562266d60 (
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
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
<!--
$FML$
$jaFML: chapter.onhost.sgml,v 1.8 2003/04/15 14:51:46 fukachan Exp $
-->
<chapter id="usage.onhost">
<title>
What can we do on the mailing list server host ?
</title>
<para>
On the host which serves ML driver,
you can use CUI and edit all configuration files as you like.
It implies you are the greatest administrator :)
</para>
<sect1>
<title>
On the host
</title>
<para>
You need no confirmation in using makefml.
</para>
<para>
Person who can login the host of mailing list server has all
priviledge for all ML's on the host.
So, He/She can edit all configuration files.
But He/She may do wrong operations.
</para>
<para>
To avoid careless miss operations, in usual cases you should use CUI
(makefml or fml) to configure fml. Of course you can edit files
directly if you can understand fml structures. By default we recommend
you should use CUI even on the host.
</para>
<para>
fml command is same as makefml command except for the argument order.
<screen>
makefml COMMAND ML OPTIONS
fml ML COMMAND OPTIONS
</screen>
Please either as you like.
</para>
</sect1>
<sect1 id="usage.commandpolicy">
<title>
Policy of command creation
</title>
<para>
&fmldevel; provides command for each function. Except for some
special cases, we should unify all functions into makefml/fml command
since such commands can be shared among CUI, GUI and commmnd mail.
</para>
<sect2>
<title>
operation may modify the specific ML (read/write).
</title>
<para>
We should implement sub-command of makefml when some operation may
modify the specific ML.
</para>
</sect2>
<sect2>
<title>
operation read only the data of the specific ML (read only).
</title>
<para>
you should implement it as a makefml command since it is related to
the specific ML.
</para>
</sect2>
<sect2>
<title>
see the general data (read only)
</title>
<para>
If the data is not related to the specific ML, for example,
see the module manual, aliases on the host,
we implement specific commands other than makefml/fml.
This command begins with ^fml.
<screen>
fmladdr [-n]
fmlalias [-n]
fmldoc MODULE
fmlconf [-n] ML
</screen>
</para>
</sect2>
<sect2>
<title>
misc
</title>
<para>
we implement specific commands other than makefml/fml.
This command begins with ^fml.
</para>
<para>
The conveter from text to html form.
This command is used to convert both fml spool and MH folders.
<screen>
fmlhtmlify [-I DIR] $src_dir $dst_dir
</screen>
</para>
</sect2>
</sect1>
§.usage.makefml;
§.usage.fml;
§.usage.fmladdr;
§.usage.fmlalias;
§.usage.fmlconf;
§.usage.fmldoc;
§.usage.fmlhtmlify;
</chapter>
|
