source: trunk/LATMOS-Accounts/man/man5/latmos-accounts.ini.pod @ 1884

Last change on this file since 1884 was 1377, checked in by nanardon, 9 years ago

Add a noDelete options to synchronization

File size: 4.1 KB
Line 
1# $Id: latmos-accounts.ini.5.pod 3186 2010-09-01 08:10:38Z nanardon $
2
3=head1 NAME
4
5latmos-accounts.ini - Main configuration file for latmos-account.
6
7=head1 DEFAULT LOCATION
8
9F</etc/latmos-accounts/latmos-accounts.ini>
10
11=head1 DESCRIPTION
12
13This config is an C<ini> like file split into section. Each section describe a
14base except sections describe bellow.
15
16=head1 [_default_] SECTION
17
18This section contains global configuration variables
19
20=head2 VARIABLES
21
22=head3 base
23
24The top level base to use by default to modify informations. The base must
25exists as a section in the configuration
26
27=head3 sync
28
29The default synchronisation to run. The synchronisation must exists as a section
30in configuration.
31
32=head3 state_dir
33
34The directory where data files will be stored
35
36=head3 smtp
37
38The SMTP server to use to send mails
39
40=head3 mailFrom
41
42The identity to use in FROM field when sending mail
43
44=head3 expire_summary_to
45
46When set, this email address will receive a summary about account expiring soon
47
48=head2 [_defattr_] SECTION
49
50Contains value assigned at object creation if the value is not specified.
51Each variable is in form C<object.attributes>.
52
53Some value can be specify for more complex auto completion:
54
55=head3 user.homebase
56
57This value is used a base directory for UNIX user home. The login is append to
58end of the value (preceded by a C</>).
59
60=head3 user.maildomain
61
62If exists set the mail attribute in form C<sn.givenName@maildomain>.
63
64=head2 [_network_]
65
66This section is used by buildnet tools, to generate network config file (DNS
67zone and dhcp).
68
69=head3 template_dir
70
71The directory containing template files
72
73=head3 output_dir
74
75The directory containing results files
76
77=head3 pre
78
79A command to execute before processing all zones
80
81=head3 post
82
83A command to run after procession all zones
84
85=head2 post_zone
86
87A command which will be run after each zone build
88
89=head2 maillog
90
91If set, must contains an email address where error will be sent in batch mode.
92
93=head2 checkzone
94
95If set generated DNS zones will be first written in a temporary files and
96checked by C<checkzone> utility.
97
98If the test fail the zone is not generated and temporary file not removed for
99analysis.
100
101=head2 named-checkzone
102
103The binary location of named-checkzone, default is C</usr/sbin/named-checkzone>.
104
105=head2 BASES SECTIONS
106
107TODO
108
109=head2 SYNCHRO SECTIONS
110
111Each synchronisation definition is identified by a section, the section name is
112prefixed by C<sync:>.
113
114=head3 from
115
116The base to use as source
117
118=head3 to
119
120The bases to synchronize, multiples bases can be specified
121
122=head3 pre
123
124A script to run before processing, if it failed, the synchronisation is not
125performed
126
127=head3 post
128
129A script to run after processing, if it failed, the synchronisation is not
130recorded as done.
131
132=head3 unexported
133
134When set, unexported object are synchronised, usefull for base supporting this
135feature (SQL only at time)
136
137=head3 noDelete
138
139Setting this parameter will make the syncronisation not deleting object in
140destination bases.
141
142Setting the C<noDelete.BASE> where C<BASE> is the name of an synchronized base
143will make this synchronisation not deleting any object into this base,
144
145Setting the C<noDelete.BASE.OTYPE> will make the synchronisation not deleting
146object type C<OTYPE> no delete into the base named C<BASE>.
147
148Example:
149
150    noDelete.MyLdap.user = yes
151
152=head3 filtering object propagation
153
154It is possible to filter the objects you want to propagate into peer base.
155
156The filter to apply must be set into the parameter named
157C<filter.BASENAME.OTYPE>, where C<BASENAME> is the name of the destination
158base and C<OTYPE> the object type to filter.
159
160For example to push into C<ldap> base only user being into group C<unix>:
161
162  filter.ldap.user = memberOf=unix
163
164
165=head3 Deleting filtered object
166
167By default filtered object will not be deleted to the destination base, neither
168touched.
169
170Setting option in form C<deletefiltered.BASENAME.OTYPE> to true will allow
171deletion. This option has effects only if filtering objects is enabled.
172
173=head1 SEE ALSO
174
175la-allowed-values.ini(5),
176la-sync-list.ini(5)
177
178=head1 AUTHOR
179
180Olivier Thauvin <olivier.thauvin@latmos.ipsl.fr>
181
182=head1 COPYRIGHT
183
184(c) LATMOS - IPSL - CNRS
185
Note: See TracBrowser for help on using the repository browser.