summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkuri igen <kuri@e4.enlightenment.org>2011-01-25 15:45:51 +0100
committerkuri igen <kuri@e4.enlightenment.org>2011-01-25 15:45:51 +0100
commitc2a6bb5b1a4ae437e11231ee637db262f78eb571 (patch)
tree426c0d60d5b551cb833db4463f6aa5bd1c43ec7f
Ajout des fichiers du projet smman
-rw-r--r--AUTHORS0
-rw-r--r--COPYING674
-rw-r--r--ChangeLog0
-rw-r--r--INSTALL365
-rw-r--r--Makefile.am49
-rw-r--r--NEWS0
-rw-r--r--README35
-rw-r--r--configure.ac50
-rw-r--r--doc/Doxyfile1689
-rw-r--r--doc/Makefile.am23
-rw-r--r--doc/gimp/intro.xcfbin0 -> 111444 bytes
-rw-r--r--doc/img/intro.pngbin0 -> 29983 bytes
-rw-r--r--rules/auth_failed4
-rw-r--r--rules/auth_success4
-rw-r--r--rules/tags_test3
-rw-r--r--rules/watch_alllog3
-rw-r--r--rules/watch_httpd3
-rw-r--r--src/Makefile.am4
-rw-r--r--src/bin/Makefile.am8
-rw-r--r--src/bin/conf.c94
-rw-r--r--src/bin/conf.h33
-rw-r--r--src/bin/date.c47
-rw-r--r--src/bin/date.h31
-rw-r--r--src/bin/global.h96
-rw-r--r--src/bin/libconf.c232
-rw-r--r--src/bin/libconf.h66
-rw-r--r--src/bin/log.txt181
-rw-r--r--src/bin/logfiles.c209
-rw-r--r--src/bin/logfiles.h40
-rw-r--r--src/bin/logmessages.c184
-rw-r--r--src/bin/logmessages.h36
-rw-r--r--src/bin/main.c178
-rw-r--r--src/bin/main.h42
-rw-r--r--src/bin/rules.c291
-rw-r--r--src/bin/rules.h47
-rw-r--r--src/bin/send.c239
-rw-r--r--src/bin/send.h38
-rw-r--r--src/bin/spy.c355
-rw-r--r--src/bin/spy.h40
39 files changed, 5393 insertions, 0 deletions
diff --git a/AUTHORS b/AUTHORS
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/AUTHORS
diff --git a/COPYING b/COPYING
new file mode 100644
index 0000000..94a9ed0
--- /dev/null
+++ b/COPYING
@@ -0,0 +1,674 @@
1 GNU GENERAL PUBLIC LICENSE
2 Version 3, 29 June 2007
3
4 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
5 Everyone is permitted to copy and distribute verbatim copies
6 of this license document, but changing it is not allowed.
7
8 Preamble
9
10 The GNU General Public License is a free, copyleft license for
11software and other kinds of works.
12
13 The licenses for most software and other practical works are designed
14to take away your freedom to share and change the works. By contrast,
15the GNU General Public License is intended to guarantee your freedom to
16share and change all versions of a program--to make sure it remains free
17software for all its users. We, the Free Software Foundation, use the
18GNU General Public License for most of our software; it applies also to
19any other work released this way by its authors. You can apply it to
20your programs, too.
21
22 When we speak of free software, we are referring to freedom, not
23price. Our General Public Licenses are designed to make sure that you
24have the freedom to distribute copies of free software (and charge for
25them if you wish), that you receive source code or can get it if you
26want it, that you can change the software or use pieces of it in new
27free programs, and that you know you can do these things.
28
29 To protect your rights, we need to prevent others from denying you
30these rights or asking you to surrender the rights. Therefore, you have
31certain responsibilities if you distribute copies of the software, or if
32you modify it: responsibilities to respect the freedom of others.
33
34 For example, if you distribute copies of such a program, whether
35gratis or for a fee, you must pass on to the recipients the same
36freedoms that you received. You must make sure that they, too, receive
37or can get the source code. And you must show them these terms so they
38know their rights.
39
40 Developers that use the GNU GPL protect your rights with two steps:
41(1) assert copyright on the software, and (2) offer you this License
42giving you legal permission to copy, distribute and/or modify it.
43
44 For the developers' and authors' protection, the GPL clearly explains
45that there is no warranty for this free software. For both users' and
46authors' sake, the GPL requires that modified versions be marked as
47changed, so that their problems will not be attributed erroneously to
48authors of previous versions.
49
50 Some devices are designed to deny users access to install or run
51modified versions of the software inside them, although the manufacturer
52can do so. This is fundamentally incompatible with the aim of
53protecting users' freedom to change the software. The systematic
54pattern of such abuse occurs in the area of products for individuals to
55use, which is precisely where it is most unacceptable. Therefore, we
56have designed this version of the GPL to prohibit the practice for those
57products. If such problems arise substantially in other domains, we
58stand ready to extend this provision to those domains in future versions
59of the GPL, as needed to protect the freedom of users.
60
61 Finally, every program is threatened constantly by software patents.
62States should not allow patents to restrict development and use of
63software on general-purpose computers, but in those that do, we wish to
64avoid the special danger that patents applied to a free program could
65make it effectively proprietary. To prevent this, the GPL assures that
66patents cannot be used to render the program non-free.
67
68 The precise terms and conditions for copying, distribution and
69modification follow.
70
71 TERMS AND CONDITIONS
72
73 0. Definitions.
74
75 "This License" refers to version 3 of the GNU General Public License.
76
77 "Copyright" also means copyright-like laws that apply to other kinds of
78works, such as semiconductor masks.
79
80 "The Program" refers to any copyrightable work licensed under this
81License. Each licensee is addressed as "you". "Licensees" and
82"recipients" may be individuals or organizations.
83
84 To "modify" a work means to copy from or adapt all or part of the work
85in a fashion requiring copyright permission, other than the making of an
86exact copy. The resulting work is called a "modified version" of the
87earlier work or a work "based on" the earlier work.
88
89 A "covered work" means either the unmodified Program or a work based
90on the Program.
91
92 To "propagate" a work means to do anything with it that, without
93permission, would make you directly or secondarily liable for
94infringement under applicable copyright law, except executing it on a
95computer or modifying a private copy. Propagation includes copying,
96distribution (with or without modification), making available to the
97public, and in some countries other activities as well.
98
99 To "convey" a work means any kind of propagation that enables other
100parties to make or receive copies. Mere interaction with a user through
101a computer network, with no transfer of a copy, is not conveying.
102
103 An interactive user interface displays "Appropriate Legal Notices"
104to the extent that it includes a convenient and prominently visible
105feature that (1) displays an appropriate copyright notice, and (2)
106tells the user that there is no warranty for the work (except to the
107extent that warranties are provided), that licensees may convey the
108work under this License, and how to view a copy of this License. If
109the interface presents a list of user commands or options, such as a
110menu, a prominent item in the list meets this criterion.
111
112 1. Source Code.
113
114 The "source code" for a work means the preferred form of the work
115for making modifications to it. "Object code" means any non-source
116form of a work.
117
118 A "Standard Interface" means an interface that either is an official
119standard defined by a recognized standards body, or, in the case of
120interfaces specified for a particular programming language, one that
121is widely used among developers working in that language.
122
123 The "System Libraries" of an executable work include anything, other
124than the work as a whole, that (a) is included in the normal form of
125packaging a Major Component, but which is not part of that Major
126Component, and (b) serves only to enable use of the work with that
127Major Component, or to implement a Standard Interface for which an
128implementation is available to the public in source code form. A
129"Major Component", in this context, means a major essential component
130(kernel, window system, and so on) of the specific operating system
131(if any) on which the executable work runs, or a compiler used to
132produce the work, or an object code interpreter used to run it.
133
134 The "Corresponding Source" for a work in object code form means all
135the source code needed to generate, install, and (for an executable
136work) run the object code and to modify the work, including scripts to
137control those activities. However, it does not include the work's
138System Libraries, or general-purpose tools or generally available free
139programs which are used unmodified in performing those activities but
140which are not part of the work. For example, Corresponding Source
141includes interface definition files associated with source files for
142the work, and the source code for shared libraries and dynamically
143linked subprograms that the work is specifically designed to require,
144such as by intimate data communication or control flow between those
145subprograms and other parts of the work.
146
147 The Corresponding Source need not include anything that users
148can regenerate automatically from other parts of the Corresponding
149Source.
150
151 The Corresponding Source for a work in source code form is that
152same work.
153
154 2. Basic Permissions.
155
156 All rights granted under this License are granted for the term of
157copyright on the Program, and are irrevocable provided the stated
158conditions are met. This License explicitly affirms your unlimited
159permission to run the unmodified Program. The output from running a
160covered work is covered by this License only if the output, given its
161content, constitutes a covered work. This License acknowledges your
162rights of fair use or other equivalent, as provided by copyright law.
163
164 You may make, run and propagate covered works that you do not
165convey, without conditions so long as your license otherwise remains
166in force. You may convey covered works to others for the sole purpose
167of having them make modifications exclusively for you, or provide you
168with facilities for running those works, provided that you comply with
169the terms of this License in conveying all material for which you do
170not control copyright. Those thus making or running the covered works
171for you must do so exclusively on your behalf, under your direction
172and control, on terms that prohibit them from making any copies of
173your copyrighted material outside their relationship with you.
174
175 Conveying under any other circumstances is permitted solely under
176the conditions stated below. Sublicensing is not allowed; section 10
177makes it unnecessary.
178
179 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
180
181 No covered work shall be deemed part of an effective technological
182measure under any applicable law fulfilling obligations under article
18311 of the WIPO copyright treaty adopted on 20 December 1996, or
184similar laws prohibiting or restricting circumvention of such
185measures.
186
187 When you convey a covered work, you waive any legal power to forbid
188circumvention of technological measures to the extent such circumvention
189is effected by exercising rights under this License with respect to
190the covered work, and you disclaim any intention to limit operation or
191modification of the work as a means of enforcing, against the work's
192users, your or third parties' legal rights to forbid circumvention of
193technological measures.
194
195 4. Conveying Verbatim Copies.
196
197 You may convey verbatim copies of the Program's source code as you
198receive it, in any medium, provided that you conspicuously and
199appropriately publish on each copy an appropriate copyright notice;
200keep intact all notices stating that this License and any
201non-permissive terms added in accord with section 7 apply to the code;
202keep intact all notices of the absence of any warranty; and give all
203recipients a copy of this License along with the Program.
204
205 You may charge any price or no price for each copy that you convey,
206and you may offer support or warranty protection for a fee.
207
208 5. Conveying Modified Source Versions.
209
210 You may convey a work based on the Program, or the modifications to
211produce it from the Program, in the form of source code under the
212terms of section 4, provided that you also meet all of these conditions:
213
214 a) The work must carry prominent notices stating that you modified
215 it, and giving a relevant date.
216
217 b) The work must carry prominent notices stating that it is
218 released under this License and any conditions added under section
219 7. This requirement modifies the requirement in section 4 to
220 "keep intact all notices".
221
222 c) You must license the entire work, as a whole, under this
223 License to anyone who comes into possession of a copy. This
224 License will therefore apply, along with any applicable section 7
225 additional terms, to the whole of the work, and all its parts,
226 regardless of how they are packaged. This License gives no
227 permission to license the work in any other way, but it does not
228 invalidate such permission if you have separately received it.
229
230 d) If the work has interactive user interfaces, each must display
231 Appropriate Legal Notices; however, if the Program has interactive
232 interfaces that do not display Appropriate Legal Notices, your
233 work need not make them do so.
234
235 A compilation of a covered work with other separate and independent
236works, which are not by their nature extensions of the covered work,
237and which are not combined with it such as to form a larger program,
238in or on a volume of a storage or distribution medium, is called an
239"aggregate" if the compilation and its resulting copyright are not
240used to limit the access or legal rights of the compilation's users
241beyond what the individual works permit. Inclusion of a covered work
242in an aggregate does not cause this License to apply to the other
243parts of the aggregate.
244
245 6. Conveying Non-Source Forms.
246
247 You may convey a covered work in object code form under the terms
248of sections 4 and 5, provided that you also convey the
249machine-readable Corresponding Source under the terms of this License,
250in one of these ways:
251
252 a) Convey the object code in, or embodied in, a physical product
253 (including a physical distribution medium), accompanied by the
254 Corresponding Source fixed on a durable physical medium
255 customarily used for software interchange.
256
257 b) Convey the object code in, or embodied in, a physical product
258 (including a physical distribution medium), accompanied by a
259 written offer, valid for at least three years and valid for as
260 long as you offer spare parts or customer support for that product
261 model, to give anyone who possesses the object code either (1) a
262 copy of the Corresponding Source for all the software in the
263 product that is covered by this License, on a durable physical
264 medium customarily used for software interchange, for a price no
265 more than your reasonable cost of physically performing this
266 conveying of source, or (2) access to copy the
267 Corresponding Source from a network server at no charge.
268
269 c) Convey individual copies of the object code with a copy of the
270 written offer to provide the Corresponding Source. This
271 alternative is allowed only occasionally and noncommercially, and
272 only if you received the object code with such an offer, in accord
273 with subsection 6b.
274
275 d) Convey the object code by offering access from a designated
276 place (gratis or for a charge), and offer equivalent access to the
277 Corresponding Source in the same way through the same place at no
278 further charge. You need not require recipients to copy the
279 Corresponding Source along with the object code. If the place to
280 copy the object code is a network server, the Corresponding Source
281 may be on a different server (operated by you or a third party)
282 that supports equivalent copying facilities, provided you maintain
283 clear directions next to the object code saying where to find the
284 Corresponding Source. Regardless of what server hosts the
285 Corresponding Source, you remain obligated to ensure that it is
286 available for as long as needed to satisfy these requirements.
287
288 e) Convey the object code using peer-to-peer transmission, provided
289 you inform other peers where the object code and Corresponding
290 Source of the work are being offered to the general public at no
291 charge under subsection 6d.
292
293 A separable portion of the object code, whose source code is excluded
294from the Corresponding Source as a System Library, need not be
295included in conveying the object code work.
296
297 A "User Product" is either (1) a "consumer product", which means any
298tangible personal property which is normally used for personal, family,
299or household purposes, or (2) anything designed or sold for incorporation
300into a dwelling. In determining whether a product is a consumer product,
301doubtful cases shall be resolved in favor of coverage. For a particular
302product received by a particular user, "normally used" refers to a
303typical or common use of that class of product, regardless of the status
304of the particular user or of the way in which the particular user
305actually uses, or expects or is expected to use, the product. A product
306is a consumer product regardless of whether the product has substantial
307commercial, industrial or non-consumer uses, unless such uses represent
308the only significant mode of use of the product.
309
310 "Installation Information" for a User Product means any methods,
311procedures, authorization keys, or other information required to install
312and execute modified versions of a covered work in that User Product from
313a modified version of its Corresponding Source. The information must
314suffice to ensure that the continued functioning of the modified object
315code is in no case prevented or interfered with solely because
316modification has been made.
317
318 If you convey an object code work under this section in, or with, or
319specifically for use in, a User Product, and the conveying occurs as
320part of a transaction in which the right of possession and use of the
321User Product is transferred to the recipient in perpetuity or for a
322fixed term (regardless of how the transaction is characterized), the
323Corresponding Source conveyed under this section must be accompanied
324by the Installation Information. But this requirement does not apply
325if neither you nor any third party retains the ability to install
326modified object code on the User Product (for example, the work has
327been installed in ROM).
328
329 The requirement to provide Installation Information does not include a
330requirement to continue to provide support service, warranty, or updates
331for a work that has been modified or installed by the recipient, or for
332the User Product in which it has been modified or installed. Access to a
333network may be denied when the modification itself materially and
334adversely affects the operation of the network or violates the rules and
335protocols for communication across the network.
336
337 Corresponding Source conveyed, and Installation Information provided,
338in accord with this section must be in a format that is publicly
339documented (and with an implementation available to the public in
340source code form), and must require no special password or key for
341unpacking, reading or copying.
342
343 7. Additional Terms.
344
345 "Additional permissions" are terms that supplement the terms of this
346License by making exceptions from one or more of its conditions.
347Additional permissions that are applicable to the entire Program shall
348be treated as though they were included in this License, to the extent
349that they are valid under applicable law. If additional permissions
350apply only to part of the Program, that part may be used separately
351under those permissions, but the entire Program remains governed by
352this License without regard to the additional permissions.
353
354 When you convey a copy of a covered work, you may at your option
355remove any additional permissions from that copy, or from any part of
356it. (Additional permissions may be written to require their own
357removal in certain cases when you modify the work.) You may place
358additional permissions on material, added by you to a covered work,
359for which you have or can give appropriate copyright permission.
360
361 Notwithstanding any other provision of this License, for material you
362add to a covered work, you may (if authorized by the copyright holders of
363that material) supplement the terms of this License with terms:
364
365 a) Disclaiming warranty or limiting liability differently from the
366 terms of sections 15 and 16 of this License; or
367
368 b) Requiring preservation of specified reasonable legal notices or
369 author attributions in that material or in the Appropriate Legal
370 Notices displayed by works containing it; or
371
372 c) Prohibiting misrepresentation of the origin of that material, or
373 requiring that modified versions of such material be marked in
374 reasonable ways as different from the original version; or
375
376 d) Limiting the use for publicity purposes of names of licensors or
377 authors of the material; or
378
379 e) Declining to grant rights under trademark law for use of some
380 trade names, trademarks, or service marks; or
381
382 f) Requiring indemnification of licensors and authors of that
383 material by anyone who conveys the material (or modified versions of
384 it) with contractual assumptions of liability to the recipient, for
385 any liability that these contractual assumptions directly impose on
386 those licensors and authors.
387
388 All other non-permissive additional terms are considered "further
389restrictions" within the meaning of section 10. If the Program as you
390received it, or any part of it, contains a notice stating that it is
391governed by this License along with a term that is a further
392restriction, you may remove that term. If a license document contains
393a further restriction but permits relicensing or conveying under this
394License, you may add to a covered work material governed by the terms
395of that license document, provided that the further restriction does
396not survive such relicensing or conveying.
397
398 If you add terms to a covered work in accord with this section, you
399must place, in the relevant source files, a statement of the
400additional terms that apply to those files, or a notice indicating
401where to find the applicable terms.
402
403 Additional terms, permissive or non-permissive, may be stated in the
404form of a separately written license, or stated as exceptions;
405the above requirements apply either way.
406
407 8. Termination.
408
409 You may not propagate or modify a covered work except as expressly
410provided under this License. Any attempt otherwise to propagate or
411modify it is void, and will automatically terminate your rights under
412this License (including any patent licenses granted under the third
413paragraph of section 11).
414
415 However, if you cease all violation of this License, then your
416license from a particular copyright holder is reinstated (a)
417provisionally, unless and until the copyright holder explicitly and
418finally terminates your license, and (b) permanently, if the copyright
419holder fails to notify you of the violation by some reasonable means
420prior to 60 days after the cessation.
421
422 Moreover, your license from a particular copyright holder is
423reinstated permanently if the copyright holder notifies you of the
424violation by some reasonable means, this is the first time you have
425received notice of violation of this License (for any work) from that
426copyright holder, and you cure the violation prior to 30 days after
427your receipt of the notice.
428
429 Termination of your rights under this section does not terminate the
430licenses of parties who have received copies or rights from you under
431this License. If your rights have been terminated and not permanently
432reinstated, you do not qualify to receive new licenses for the same
433material under section 10.
434
435 9. Acceptance Not Required for Having Copies.
436
437 You are not required to accept this License in order to receive or
438run a copy of the Program. Ancillary propagation of a covered work
439occurring solely as a consequence of using peer-to-peer transmission
440to receive a copy likewise does not require acceptance. However,
441nothing other than this License grants you permission to propagate or
442modify any covered work. These actions infringe copyright if you do
443not accept this License. Therefore, by modifying or propagating a
444covered work, you indicate your acceptance of this License to do so.
445
446 10. Automatic Licensing of Downstream Recipients.
447
448 Each time you convey a covered work, the recipient automatically
449receives a license from the original licensors, to run, modify and
450propagate that work, subject to this License. You are not responsible
451for enforcing compliance by third parties with this License.
452
453 An "entity transaction" is a transaction transferring control of an
454organization, or substantially all assets of one, or subdividing an
455organization, or merging organizations. If propagation of a covered
456work results from an entity transaction, each party to that
457transaction who receives a copy of the work also receives whatever
458licenses to the work the party's predecessor in interest had or could
459give under the previous paragraph, plus a right to possession of the
460Corresponding Source of the work from the predecessor in interest, if
461the predecessor has it or can get it with reasonable efforts.
462
463 You may not impose any further restrictions on the exercise of the
464rights granted or affirmed under this License. For example, you may
465not impose a license fee, royalty, or other charge for exercise of
466rights granted under this License, and you may not initiate litigation
467(including a cross-claim or counterclaim in a lawsuit) alleging that
468any patent claim is infringed by making, using, selling, offering for
469sale, or importing the Program or any portion of it.
470
471 11. Patents.
472
473 A "contributor" is a copyright holder who authorizes use under this
474License of the Program or a work on which the Program is based. The
475work thus licensed is called the contributor's "contributor version".
476
477 A contributor's "essential patent claims" are all patent claims
478owned or controlled by the contributor, whether already acquired or
479hereafter acquired, that would be infringed by some manner, permitted
480by this License, of making, using, or selling its contributor version,
481but do not include claims that would be infringed only as a
482consequence of further modification of the contributor version. For
483purposes of this definition, "control" includes the right to grant
484patent sublicenses in a manner consistent with the requirements of
485this License.
486
487 Each contributor grants you a non-exclusive, worldwide, royalty-free
488patent license under the contributor's essential patent claims, to
489make, use, sell, offer for sale, import and otherwise run, modify and
490propagate the contents of its contributor version.
491
492 In the following three paragraphs, a "patent license" is any express
493agreement or commitment, however denominated, not to enforce a patent
494(such as an express permission to practice a patent or covenant not to
495sue for patent infringement). To "grant" such a patent license to a
496party means to make such an agreement or commitment not to enforce a
497patent against the party.
498
499 If you convey a covered work, knowingly relying on a patent license,
500and the Corresponding Source of the work is not available for anyone
501to copy, free of charge and under the terms of this License, through a
502publicly available network server or other readily accessible means,
503then you must either (1) cause the Corresponding Source to be so
504available, or (2) arrange to deprive yourself of the benefit of the
505patent license for this particular work, or (3) arrange, in a manner
506consistent with the requirements of this License, to extend the patent
507license to downstream recipients. "Knowingly relying" means you have
508actual knowledge that, but for the patent license, your conveying the
509covered work in a country, or your recipient's use of the covered work
510in a country, would infringe one or more identifiable patents in that
511country that you have reason to believe are valid.
512
513 If, pursuant to or in connection with a single transaction or
514arrangement, you convey, or propagate by procuring conveyance of, a
515covered work, and grant a patent license to some of the parties
516receiving the covered work authorizing them to use, propagate, modify
517or convey a specific copy of the covered work, then the patent license
518you grant is automatically extended to all recipients of the covered
519work and works based on it.
520
521 A patent license is "discriminatory" if it does not include within
522the scope of its coverage, prohibits the exercise of, or is
523conditioned on the non-exercise of one or more of the rights that are
524specifically granted under this License. You may not convey a covered
525work if you are a party to an arrangement with a third party that is
526in the business of distributing software, under which you make payment
527to the third party based on the extent of your activity of conveying
528the work, and under which the third party grants, to any of the
529parties who would receive the covered work from you, a discriminatory
530patent license (a) in connection with copies of the covered work
531conveyed by you (or copies made from those copies), or (b) primarily
532for and in connection with specific products or compilations that
533contain the covered work, unless you entered into that arrangement,
534or that patent license was granted, prior to 28 March 2007.
535
536 Nothing in this License shall be construed as excluding or limiting
537any implied license or other defenses to infringement that may
538otherwise be available to you under applicable patent law.
539
540 12. No Surrender of Others' Freedom.
541
542 If conditions are imposed on you (whether by court order, agreement or
543otherwise) that contradict the conditions of this License, they do not
544excuse you from the conditions of this License. If you cannot convey a
545covered work so as to satisfy simultaneously your obligations under this
546License and any other pertinent obligations, then as a consequence you may
547not convey it at all. For example, if you agree to terms that obligate you
548to collect a royalty for further conveying from those to whom you convey
549the Program, the only way you could satisfy both those terms and this
550License would be to refrain entirely from conveying the Program.
551
552 13. Use with the GNU Affero General Public License.
553
554 Notwithstanding any other provision of this License, you have
555permission to link or combine any covered work with a work licensed
556under version 3 of the GNU Affero General Public License into a single
557combined work, and to convey the resulting work. The terms of this
558License will continue to apply to the part which is the covered work,
559but the special requirements of the GNU Affero General Public License,
560section 13, concerning interaction through a network will apply to the
561combination as such.
562
563 14. Revised Versions of this License.
564
565 The Free Software Foundation may publish revised and/or new versions of
566the GNU General Public License from time to time. Such new versions will
567be similar in spirit to the present version, but may differ in detail to
568address new problems or concerns.
569
570 Each version is given a distinguishing version number. If the
571Program specifies that a certain numbered version of the GNU General
572Public License "or any later version" applies to it, you have the
573option of following the terms and conditions either of that numbered
574version or of any later version published by the Free Software
575Foundation. If the Program does not specify a version number of the
576GNU General Public License, you may choose any version ever published
577by the Free Software Foundation.
578
579 If the Program specifies that a proxy can decide which future
580versions of the GNU General Public License can be used, that proxy's
581public statement of acceptance of a version permanently authorizes you
582to choose that version for the Program.
583
584 Later license versions may give you additional or different
585permissions. However, no additional obligations are imposed on any
586author or copyright holder as a result of your choosing to follow a
587later version.
588
589 15. Disclaimer of Warranty.
590
591 THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
592APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
593HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
594OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
595THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
596PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
597IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
598ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
599
600 16. Limitation of Liability.
601
602 IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
603WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
604THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
605GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
606USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
607DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
608PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
609EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
610SUCH DAMAGES.
611
612 17. Interpretation of Sections 15 and 16.
613
614 If the disclaimer of warranty and limitation of liability provided
615above cannot be given local legal effect according to their terms,
616reviewing courts shall apply local law that most closely approximates
617an absolute waiver of all civil liability in connection with the
618Program, unless a warranty or assumption of liability accompanies a
619copy of the Program in return for a fee.
620
621 END OF TERMS AND CONDITIONS
622
623 How to Apply These Terms to Your New Programs
624
625 If you develop a new program, and you want it to be of the greatest
626possible use to the public, the best way to achieve this is to make it
627free software which everyone can redistribute and change under these terms.
628
629 To do so, attach the following notices to the program. It is safest
630to attach them to the start of each source file to most effectively
631state the exclusion of warranty; and each file should have at least
632the "copyright" line and a pointer to where the full notice is found.
633
634 <one line to give the program's name and a brief idea of what it does.>
635 Copyright (C) <year> <name of author>
636
637 This program is free software: you can redistribute it and/or modify
638 it under the terms of the GNU General Public License as published by
639 the Free Software Foundation, either version 3 of the License, or
640 (at your option) any later version.
641
642 This program is distributed in the hope that it will be useful,
643 but WITHOUT ANY WARRANTY; without even the implied warranty of
644 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
645 GNU General Public License for more details.
646
647 You should have received a copy of the GNU General Public License
648 along with this program. If not, see <http://www.gnu.org/licenses/>.
649
650Also add information on how to contact you by electronic and paper mail.
651
652 If the program does terminal interaction, make it output a short
653notice like this when it starts in an interactive mode:
654
655 <program> Copyright (C) <year> <name of author>
656 This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
657 This is free software, and you are welcome to redistribute it
658 under certain conditions; type `show c' for details.
659
660The hypothetical commands `show w' and `show c' should show the appropriate
661parts of the General Public License. Of course, your program's commands
662might be different; for a GUI interface, you would use an "about box".
663
664 You should also get your employer (if you work as a programmer) or school,
665if any, to sign a "copyright disclaimer" for the program, if necessary.
666For more information on this, and how to apply and follow the GNU GPL, see
667<http://www.gnu.org/licenses/>.
668
669 The GNU General Public License does not permit incorporating your program
670into proprietary programs. If your program is a subroutine library, you
671may consider it more useful to permit linking proprietary applications with
672the library. If this is what you want to do, use the GNU Lesser General
673Public License instead of this License. But first, please read
674<http://www.gnu.org/philosophy/why-not-lgpl.html>.
diff --git a/ChangeLog b/ChangeLog
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/ChangeLog
diff --git a/INSTALL b/INSTALL
new file mode 100644
index 0000000..7d1c323
--- /dev/null
+++ b/INSTALL
@@ -0,0 +1,365 @@
1Installation Instructions
2*************************
3
4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
52006, 2007, 2008, 2009 Free Software Foundation, Inc.
6
7 Copying and distribution of this file, with or without modification,
8are permitted in any medium without royalty provided the copyright
9notice and this notice are preserved. This file is offered as-is,
10without warranty of any kind.
11
12Basic Installation
13==================
14
15 Briefly, the shell commands `./configure; make; make install' should
16configure, build, and install this package. The following
17more-detailed instructions are generic; see the `README' file for
18instructions specific to this package. Some packages provide this
19`INSTALL' file but do not implement all of the features documented
20below. The lack of an optional feature in a given package is not
21necessarily a bug. More recommendations for GNU packages can be found
22in *note Makefile Conventions: (standards)Makefile Conventions.
23
24 The `configure' shell script attempts to guess correct values for
25various system-dependent variables used during compilation. It uses
26those values to create a `Makefile' in each directory of the package.
27It may also create one or more `.h' files containing system-dependent
28definitions. Finally, it creates a shell script `config.status' that
29you can run in the future to recreate the current configuration, and a
30file `config.log' containing compiler output (useful mainly for
31debugging `configure').
32
33 It can also use an optional file (typically called `config.cache'
34and enabled with `--cache-file=config.cache' or simply `-C') that saves
35the results of its tests to speed up reconfiguring. Caching is
36disabled by default to prevent problems with accidental use of stale
37cache files.
38
39 If you need to do unusual things to compile the package, please try
40to figure out how `configure' could check whether to do them, and mail
41diffs or instructions to the address given in the `README' so they can
42be considered for the next release. If you are using the cache, and at
43some point `config.cache' contains results you don't want to keep, you
44may remove or edit it.
45
46 The file `configure.ac' (or `configure.in') is used to create
47`configure' by a program called `autoconf'. You need `configure.ac' if
48you want to change it or regenerate `configure' using a newer version
49of `autoconf'.
50
51 The simplest way to compile this package is:
52
53 1. `cd' to the directory containing the package's source code and type
54 `./configure' to configure the package for your system.
55
56 Running `configure' might take a while. While running, it prints
57 some messages telling which features it is checking for.
58
59 2. Type `make' to compile the package.
60
61 3. Optionally, type `make check' to run any self-tests that come with
62 the package, generally using the just-built uninstalled binaries.
63
64 4. Type `make install' to install the programs and any data files and
65 documentation. When installing into a prefix owned by root, it is
66 recommended that the package be configured and built as a regular
67 user, and only the `make install' phase executed with root
68 privileges.
69
70 5. Optionally, type `make installcheck' to repeat any self-tests, but
71 this time using the binaries in their final installed location.
72 This target does not install anything. Running this target as a
73 regular user, particularly if the prior `make install' required
74 root privileges, verifies that the installation completed
75 correctly.
76
77 6. You can remove the program binaries and object files from the
78 source code directory by typing `make clean'. To also remove the
79 files that `configure' created (so you can compile the package for
80 a different kind of computer), type `make distclean'. There is
81 also a `make maintainer-clean' target, but that is intended mainly
82 for the package's developers. If you use it, you may have to get
83 all sorts of other programs in order to regenerate files that came
84 with the distribution.
85
86 7. Often, you can also type `make uninstall' to remove the installed
87 files again. In practice, not all packages have tested that
88 uninstallation works correctly, even though it is required by the
89 GNU Coding Standards.
90
91 8. Some packages, particularly those that use Automake, provide `make
92 distcheck', which can by used by developers to test that all other
93 targets like `make install' and `make uninstall' work correctly.
94 This target is generally not run by end users.
95
96Compilers and Options
97=====================
98
99 Some systems require unusual options for compilation or linking that
100the `configure' script does not know about. Run `./configure --help'
101for details on some of the pertinent environment variables.
102
103 You can give `configure' initial values for configuration parameters
104by setting variables in the command line or in the environment. Here
105is an example:
106
107 ./configure CC=c99 CFLAGS=-g LIBS=-lposix
108
109 *Note Defining Variables::, for more details.
110
111Compiling For Multiple Architectures
112====================================
113
114 You can compile the package for more than one kind of computer at the
115same time, by placing the object files for each architecture in their
116own directory. To do this, you can use GNU `make'. `cd' to the
117directory where you want the object files and executables to go and run
118the `configure' script. `configure' automatically checks for the
119source code in the directory that `configure' is in and in `..'. This
120is known as a "VPATH" build.
121
122 With a non-GNU `make', it is safer to compile the package for one
123architecture at a time in the source code directory. After you have
124installed the package for one architecture, use `make distclean' before
125reconfiguring for another architecture.
126
127 On MacOS X 10.5 and later systems, you can create libraries and
128executables that work on multiple system types--known as "fat" or
129"universal" binaries--by specifying multiple `-arch' options to the
130compiler but only a single `-arch' option to the preprocessor. Like
131this:
132
133 ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
134 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
135 CPP="gcc -E" CXXCPP="g++ -E"
136
137 This is not guaranteed to produce working output in all cases, you
138may have to build one architecture at a time and combine the results
139using the `lipo' tool if you have problems.
140
141Installation Names
142==================
143
144 By default, `make install' installs the package's commands under
145`/usr/local/bin', include files under `/usr/local/include', etc. You
146can specify an installation prefix other than `/usr/local' by giving
147`configure' the option `--prefix=PREFIX', where PREFIX must be an
148absolute file name.
149
150 You can specify separate installation prefixes for
151architecture-specific files and architecture-independent files. If you
152pass the option `--exec-prefix=PREFIX' to `configure', the package uses
153PREFIX as the prefix for installing programs and libraries.
154Documentation and other data files still use the regular prefix.
155
156 In addition, if you use an unusual directory layout you can give
157options like `--bindir=DIR' to specify different values for particular
158kinds of files. Run `configure --help' for a list of the directories
159you can set and what kinds of files go in them. In general, the
160default for these options is expressed in terms of `${prefix}', so that
161specifying just `--prefix' will affect all of the other directory
162specifications that were not explicitly provided.
163
164 The most portable way to affect installation locations is to pass the
165correct locations to `configure'; however, many packages provide one or
166both of the following shortcuts of passing variable assignments to the
167`make install' command line to change installation locations without
168having to reconfigure or recompile.
169
170 The first method involves providing an override variable for each
171affected directory. For example, `make install
172prefix=/alternate/directory' will choose an alternate location for all
173directory configuration variables that were expressed in terms of
174`${prefix}'. Any directories that were specified during `configure',
175but not in terms of `${prefix}', must each be overridden at install
176time for the entire installation to be relocated. The approach of
177makefile variable overrides for each directory variable is required by
178the GNU Coding Standards, and ideally causes no recompilation.
179However, some platforms have known limitations with the semantics of
180shared libraries that end up requiring recompilation when using this
181method, particularly noticeable in packages that use GNU Libtool.
182
183 The second method involves providing the `DESTDIR' variable. For
184example, `make install DESTDIR=/alternate/directory' will prepend
185`/alternate/directory' before all installation names. The approach of
186`DESTDIR' overrides is not required by the GNU Coding Standards, and
187does not work on platforms that have drive letters. On the other hand,
188it does better at avoiding recompilation issues, and works well even
189when some directory options were not specified in terms of `${prefix}'
190at `configure' time.
191
192Optional Features
193=================
194
195 If the package supports it, you can cause programs to be installed
196with an extra prefix or suffix on their names by giving `configure' the
197option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
198
199 Some packages pay attention to `--enable-FEATURE' options to
200`configure', where FEATURE indicates an optional part of the package.
201They may also pay attention to `--with-PACKAGE' options, where PACKAGE
202is something like `gnu-as' or `x' (for the X Window System). The
203`README' should mention any `--enable-' and `--with-' options that the
204package recognizes.
205
206 For packages that use the X Window System, `configure' can usually
207find the X include and library files automatically, but if it doesn't,
208you can use the `configure' options `--x-includes=DIR' and
209`--x-libraries=DIR' to specify their locations.
210
211 Some packages offer the ability to configure how verbose the
212execution of `make' will be. For these packages, running `./configure
213--enable-silent-rules' sets the default to minimal output, which can be
214overridden with `make V=1'; while running `./configure
215--disable-silent-rules' sets the default to verbose, which can be
216overridden with `make V=0'.
217
218Particular systems
219==================
220
221 On HP-UX, the default C compiler is not ANSI C compatible. If GNU
222CC is not installed, it is recommended to use the following options in
223order to use an ANSI C compiler:
224
225 ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
226
227and if that doesn't work, install pre-built binaries of GCC for HP-UX.
228
229 On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
230parse its `<wchar.h>' header file. The option `-nodtk' can be used as
231a workaround. If GNU CC is not installed, it is therefore recommended
232to try
233
234 ./configure CC="cc"
235
236and if that doesn't work, try
237
238 ./configure CC="cc -nodtk"
239
240 On Solaris, don't put `/usr/ucb' early in your `PATH'. This
241directory contains several dysfunctional programs; working variants of
242these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
243in your `PATH', put it _after_ `/usr/bin'.
244
245 On Haiku, software installed for all users goes in `/boot/common',
246not `/usr/local'. It is recommended to use the following options:
247
248 ./configure --prefix=/boot/common
249
250Specifying the System Type
251==========================
252
253 There may be some features `configure' cannot figure out
254automatically, but needs to determine by the type of machine the package
255will run on. Usually, assuming the package is built to be run on the
256_same_ architectures, `configure' can figure that out, but if it prints
257a message saying it cannot guess the machine type, give it the
258`--build=TYPE' option. TYPE can either be a short name for the system
259type, such as `sun4', or a canonical name which has the form:
260
261 CPU-COMPANY-SYSTEM
262
263where SYSTEM can have one of these forms:
264
265 OS
266 KERNEL-OS
267
268 See the file `config.sub' for the possible values of each field. If
269`config.sub' isn't included in this package, then this package doesn't
270need to know the machine type.
271
272 If you are _building_ compiler tools for cross-compiling, you should
273use the option `--target=TYPE' to select the type of system they will
274produce code for.
275
276 If you want to _use_ a cross compiler, that generates code for a
277platform different from the build platform, you should specify the
278"host" platform (i.e., that on which the generated programs will
279eventually be run) with `--host=TYPE'.
280
281Sharing Defaults
282================
283
284 If you want to set default values for `configure' scripts to share,
285you can create a site shell script called `config.site' that gives
286default values for variables like `CC', `cache_file', and `prefix'.
287`configure' looks for `PREFIX/share/config.site' if it exists, then
288`PREFIX/etc/config.site' if it exists. Or, you can set the
289`CONFIG_SITE' environment variable to the location of the site script.
290A warning: not all `configure' scripts look for a site script.
291
292Defining Variables
293==================
294
295 Variables not defined in a site shell script can be set in the
296environment passed to `configure'. However, some packages may run
297configure again during the build, and the customized values of these
298variables may be lost. In order to avoid this problem, you should set
299them in the `configure' command line, using `VAR=value'. For example:
300
301 ./configure CC=/usr/local2/bin/gcc
302
303causes the specified `gcc' to be used as the C compiler (unless it is
304overridden in the site shell script).
305
306Unfortunately, this technique does not work for `CONFIG_SHELL' due to
307an Autoconf bug. Until the bug is fixed you can use this workaround:
308
309 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
310
311`configure' Invocation
312======================
313
314 `configure' recognizes the following options to control how it
315operates.
316
317`--help'
318`-h'
319 Print a summary of all of the options to `configure', and exit.
320
321`--help=short'
322`--help=recursive'
323 Print a summary of the options unique to this package's
324 `configure', and exit. The `short' variant lists options used
325 only in the top level, while the `recursive' variant lists options
326 also present in any nested packages.
327
328`--version'
329`-V'
330 Print the version of Autoconf used to generate the `configure'
331 script, and exit.
332
333`--cache-file=FILE'
334 Enable the cache: use and save the results of the tests in FILE,
335 traditionally `config.cache'. FILE defaults to `/dev/null' to
336 disable caching.
337
338`--config-cache'
339`-C'
340 Alias for `--cache-file=config.cache'.
341
342`--quiet'
343`--silent'
344`-q'
345 Do not print messages saying which checks are being made. To
346 suppress all normal output, redirect it to `/dev/null' (any error
347 messages will still be shown).
348
349`--srcdir=DIR'
350 Look for the package's source code in directory DIR. Usually
351 `configure' can determine that directory automatically.
352
353`--prefix=DIR'
354 Use DIR as the installation prefix. *note Installation Names::
355 for more details, including other options available for fine-tuning
356 the installation locations.
357
358`--no-create'
359`-n'
360 Run the configure checks, but stop before creating any output
361 files.
362
363`configure' also accepts some other, not widely useful, options. Run
364`configure --help' for more details.
365
diff --git a/Makefile.am b/Makefile.am
new file mode 100644
index 0000000..8a2a527
--- /dev/null
+++ b/Makefile.am
@@ -0,0 +1,49 @@
1ACLOCAL_AMFLAGS = -I m4
2
3SUBDIRS = src doc
4
5MAINTAINERCLEANFILES = \
6ABOUT-NLS \
7Makefile.in \
8aclocal.m4 \
9autom4te.cache \
10config.guess \
11config.h.in \
12config.h.in~ \
13config.rpath \
14config.sub \
15configure \
16depcomp \
17install-sh \
18ltmain.sh \
19missing \
20mkinstalldirs \
21$(PACKAGE_TARNAME)-$(PACKAGE_VERSION).tar.gz \
22$(PACKAGE_TARNAME)-$(PACKAGE_VERSION).tar.bz2 \
23$(PACKAGE_TARNAME)-$(PACKAGE_VERSION)-doc.tar.bz2 \
24m4/libtool.m4 \
25m4/lt~obsolete.m4 \
26m4/ltoptions.m4 \
27m4/ltsugar.m4 \
28m4/ltversion.m4 \
29m4/codeset.m4 \
30m4/gettext.m4 \
31m4/glibc21.m4 \
32m4/iconv.m4 \
33m4/intdiv0.m4 \
34m4/inttypes_h.m4 \
35m4/inttypes.m4 \
36m4/inttypes-pri.m4 \
37m4/isc-posix.m4 \
38m4/lcmessage.m4 \
39m4/lib-ld.m4 \
40m4/lib-link.m4 \
41m4/lib-prefix.m4 \
42m4/nls.m4 \
43m4/po.m4 \
44m4/progtest.m4 \
45m4/stdint_h.m4 \
46m4/uintmax_t.m4 \
47m4/ulonglong.m4
48
49
diff --git a/NEWS b/NEWS
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/NEWS
diff --git a/README b/README
new file mode 100644
index 0000000..55c37f9
--- /dev/null
+++ b/README
@@ -0,0 +1,35 @@
1If you use it on a fresh install, with a non existant DB, you have to build it :
2
3curl -XPUT http://YOURSERVER:9200/YOURINDEX/ -d '
4{
5 "settings":
6 {
7 "events":
8 {
9 "mappings":
10 {
11 "@source":
12 {"type":"string"},
13 "@source_host":
14 {"type":"string"},
15 "@source_path":
16 {"type":"string"},
17 "@timestamp":
18 {"type":"date"},
19 "@tags":
20 {"type":"string"},
21 "@message":
22 {"type":"string"},
23 "@fields":
24 {
25 "type":"object",
26 "properties":
27 {
28 "HOSTNAME":
29 {"type":"string"}
30 }
31 }
32 }
33 }
34 }
35}'
diff --git a/configure.ac b/configure.ac
new file mode 100644
index 0000000..32333d9
--- /dev/null
+++ b/configure.ac
@@ -0,0 +1,50 @@
1m4_define([v_rev], m4_esyscmd([(svnversion "." | grep -v exported || echo 0) | tr -d ' MSP\n']))
2
3AC_INIT([Smman], [1.0], [guillaume.friloux@asp64.com])
4
5AC_PREREQ(2.01)
6AC_CONFIG_SRCDIR([configure.ac])
7
8AM_INIT_AUTOMAKE([1.6 dist-bzip2])
9
10define([AC_LIBTOOL_LANG_CXX_CONFIG], [:])dnl
11define([AC_LIBTOOL_LANG_F77_CONFIG], [:])dnl
12AC_PROG_LIBTOOL
13AC_CONFIG_MACRO_DIR([m4])
14
15dnl we just have set the version info, then:
16version_number=1.0
17revision_number="v_rev"
18AC_SUBST(version_number)
19AC_SUBST(revision_number)
20
21AC_PROG_CC
22
23AC_CONFIG_FILES([
24Makefile
25doc/Makefile
26src/Makefile
27src/bin/Makefile
28])
29
30
31PKG_CHECK_MODULES([eina], [eina], [have_eina="yes"], [have_eina="no"])
32PKG_CHECK_MODULES([ecore], [ecore ecore-file], [have_ecore="yes"], [have_ecore="no"])
33PKG_CHECK_MODULES([libcurl], [libcurl], [have_curl="yes"], [have_curl="no"])
34AC_OUTPUT
35
36echo
37echo
38echo "------------------------------------------------------------------------"
39echo "$PACKAGE_NAME $PACKAGE_VERSION"
40echo "------------------------------------------------------------------------"
41echo
42echo "Configuration Options Summary:"
43echo
44echo " eina.........: ${have_eina}"
45echo " ecore........: ${have_ecore}"
46echo " curl.........: ${have_curl}"
47echo
48echo " prefix.......: $prefix"
49echo
50
diff --git a/doc/Doxyfile b/doc/Doxyfile
new file mode 100644
index 0000000..ed04dea
--- /dev/null
+++ b/doc/Doxyfile
@@ -0,0 +1,1689 @@
1# Doxyfile 1.7.2
2
3# This file describes the settings to be used by the documentation system
4# doxygen (www.doxygen.org) for a project
5#
6# All text after a hash (#) is considered a comment and will be ignored
7# The format is:
8# TAG = value [value, ...]
9# For lists items can also be appended using:
10# TAG += value [value, ...]
11# Values that contain spaces should be placed between quotes (" ")
12
13#---------------------------------------------------------------------------
14# Project related configuration options
15#---------------------------------------------------------------------------
16
17# This tag specifies the encoding used for all characters in the config file
18# that follow. The default is UTF-8 which is also the encoding used for all
19# text before the first occurrence of this tag. Doxygen uses libiconv (or the
20# iconv built into libc) for the transcoding. See
21# http://www.gnu.org/software/libiconv for the list of possible encodings.
22
23DOXYFILE_ENCODING = UTF-8
24
25# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
26# by quotes) that should identify the project.
27
28PROJECT_NAME = SMMan
29
30# The PROJECT_NUMBER tag can be used to enter a project or revision number.
31# This could be handy for archiving the generated documentation or
32# if some version control system is used.
33
34PROJECT_NUMBER =
35
36# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
37# base path where the generated documentation will be put.
38# If a relative path is entered, it will be relative to the location
39# where doxygen was started. If left blank the current directory will be used.
40
41OUTPUT_DIRECTORY = ./
42
43# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
44# 4096 sub-directories (in 2 levels) under the output directory of each output
45# format and will distribute the generated files over these directories.
46# Enabling this option can be useful when feeding doxygen a huge amount of
47# source files, where putting all generated files in the same directory would
48# otherwise cause performance problems for the file system.
49
50CREATE_SUBDIRS = NO
51
52# The OUTPUT_LANGUAGE tag is used to specify the language in which all
53# documentation generated by doxygen is written. Doxygen will use this
54# information to generate all constant output in the proper language.
55# The default language is English, other supported languages are:
56# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
57# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
58# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
59# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
60# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak,
61# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
62
63OUTPUT_LANGUAGE = English
64
65# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
66# include brief member descriptions after the members that are listed in
67# the file and class documentation (similar to JavaDoc).
68# Set to NO to disable this.
69
70BRIEF_MEMBER_DESC = YES
71
72# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
73# the brief description of a member or function before the detailed description.
74# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
75# brief descriptions will be completely suppressed.
76
77REPEAT_BRIEF = YES
78
79# This tag implements a quasi-intelligent brief description abbreviator
80# that is used to form the text in various listings. Each string
81# in this list, if found as the leading text of the brief description, will be
82# stripped from the text and the result after processing the whole list, is
83# used as the annotated text. Otherwise, the brief description is used as-is.
84# If left blank, the following values are used ("$name" is automatically
85# replaced with the name of the entity): "The $name class" "The $name widget"
86# "The $name file" "is" "provides" "specifies" "contains"
87# "represents" "a" "an" "the"
88
89ABBREVIATE_BRIEF = "The $name class" \
90 "The $name widget" \
91 "The $name file" \
92 is \
93 provides \
94 specifies \
95 contains \
96 represents \
97 a \
98 an \
99 the
100
101# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
102# Doxygen will generate a detailed section even if there is only a brief
103# description.
104
105ALWAYS_DETAILED_SEC = NO
106
107# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
108# inherited members of a class in the documentation of that class as if those
109# members were ordinary class members. Constructors, destructors and assignment
110# operators of the base classes will not be shown.
111
112INLINE_INHERITED_MEMB = NO
113
114# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
115# path before files name in the file list and in the header files. If set
116# to NO the shortest path that makes the file name unique will be used.
117
118FULL_PATH_NAMES = YES
119
120# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
121# can be used to strip a user-defined part of the path. Stripping is
122# only done if one of the specified strings matches the left-hand part of
123# the path. The tag can be used to show relative paths in the file list.
124# If left blank the directory from which doxygen is run is used as the
125# path to strip.
126
127STRIP_FROM_PATH =
128
129# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
130# the path mentioned in the documentation of a class, which tells
131# the reader which header file to include in order to use a class.
132# If left blank only the name of the header file containing the class
133# definition is used. Otherwise one should specify the include paths that
134# are normally passed to the compiler using the -I flag.
135
136STRIP_FROM_INC_PATH =
137
138# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
139# (but less readable) file names. This can be useful if your file system
140# doesn't support long names like on DOS, Mac, or CD-ROM.
141
142SHORT_NAMES = NO
143
144# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
145# will interpret the first line (until the first dot) of a JavaDoc-style
146# comment as the brief description. If set to NO, the JavaDoc
147# comments will behave just like regular Qt-style comments
148# (thus requiring an explicit @brief command for a brief description.)
149
150JAVADOC_AUTOBRIEF = NO
151
152# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
153# interpret the first line (until the first dot) of a Qt-style
154# comment as the brief description. If set to NO, the comments
155# will behave just like regular Qt-style comments (thus requiring
156# an explicit \brief command for a brief description.)
157
158QT_AUTOBRIEF = NO
159
160# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
161# treat a multi-line C++ special comment block (i.e. a block of //! or ///
162# comments) as a brief description. This used to be the default behaviour.
163# The new default is to treat a multi-line C++ comment block as a detailed
164# description. Set this tag to YES if you prefer the old behaviour instead.
165
166MULTILINE_CPP_IS_BRIEF = NO
167
168# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
169# member inherits the documentation from any documented member that it
170# re-implements.
171
172INHERIT_DOCS = YES
173
174# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
175# a new page for each member. If set to NO, the documentation of a member will
176# be part of the file/class/namespace that contains it.
177
178SEPARATE_MEMBER_PAGES = NO
179
180# The TAB_SIZE tag can be used to set the number of spaces in a tab.
181# Doxygen uses this value to replace tabs by spaces in code fragments.
182
183TAB_SIZE = 8
184
185# This tag can be used to specify a number of aliases that acts
186# as commands in the documentation. An alias has the form "name=value".
187# For example adding "sideeffect=\par Side Effects:\n" will allow you to
188# put the command \sideeffect (or @sideeffect) in the documentation, which
189# will result in a user-defined paragraph with heading "Side Effects:".
190# You can put \n's in the value part of an alias to insert newlines.
191
192ALIASES =
193
194# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
195# sources only. Doxygen will then generate output that is more tailored for C.
196# For instance, some of the names that are used will be different. The list
197# of all members will be omitted, etc.
198
199OPTIMIZE_OUTPUT_FOR_C = NO
200
201# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
202# sources only. Doxygen will then generate output that is more tailored for
203# Java. For instance, namespaces will be presented as packages, qualified
204# scopes will look different, etc.
205
206OPTIMIZE_OUTPUT_JAVA = NO
207
208# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
209# sources only. Doxygen will then generate output that is more tailored for
210# Fortran.
211
212OPTIMIZE_FOR_FORTRAN = NO
213
214# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
215# sources. Doxygen will then generate output that is tailored for
216# VHDL.
217
218OPTIMIZE_OUTPUT_VHDL = NO
219
220# Doxygen selects the parser to use depending on the extension of the files it
221# parses. With this tag you can assign which parser to use for a given extension.
222# Doxygen has a built-in mapping, but you can override or extend it using this
223# tag. The format is ext=language, where ext is a file extension, and language
224# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,
225# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make
226# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
227# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions
228# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
229
230EXTENSION_MAPPING =
231
232# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
233# to include (a tag file for) the STL sources as input, then you should
234# set this tag to YES in order to let doxygen match functions declarations and
235# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
236# func(std::string) {}). This also makes the inheritance and collaboration
237# diagrams that involve STL classes more complete and accurate.
238
239BUILTIN_STL_SUPPORT = NO
240
241# If you use Microsoft's C++/CLI language, you should set this option to YES to
242# enable parsing support.
243
244CPP_CLI_SUPPORT = NO
245
246# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
247# Doxygen will parse them like normal C++ but will assume all classes use public
248# instead of private inheritance when no explicit protection keyword is present.
249
250SIP_SUPPORT = NO
251
252# For Microsoft's IDL there are propget and propput attributes to indicate getter
253# and setter methods for a property. Setting this option to YES (the default)
254# will make doxygen replace the get and set methods by a property in the
255# documentation. This will only work if the methods are indeed getting or
256# setting a simple type. If this is not the case, or you want to show the
257# methods anyway, you should set this option to NO.
258
259IDL_PROPERTY_SUPPORT = YES
260
261# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
262# tag is set to YES, then doxygen will reuse the documentation of the first
263# member in the group (if any) for the other members of the group. By default
264# all members of a group must be documented explicitly.
265
266DISTRIBUTE_GROUP_DOC = NO
267
268# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
269# the same type (for instance a group of public functions) to be put as a
270# subgroup of that type (e.g. under the Public Functions section). Set it to
271# NO to prevent subgrouping. Alternatively, this can be done per class using
272# the \nosubgrouping command.
273
274SUBGROUPING = YES
275
276# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
277# is documented as struct, union, or enum with the name of the typedef. So
278# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
279# with name TypeT. When disabled the typedef will appear as a member of a file,
280# namespace, or class. And the struct will be named TypeS. This can typically
281# be useful for C code in case the coding convention dictates that all compound
282# types are typedef'ed and only the typedef is referenced, never the tag name.
283
284TYPEDEF_HIDES_STRUCT = NO
285
286# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
287# determine which symbols to keep in memory and which to flush to disk.
288# When the cache is full, less often used symbols will be written to disk.
289# For small to medium size projects (<1000 input files) the default value is
290# probably good enough. For larger projects a too small cache size can cause
291# doxygen to be busy swapping symbols to and from disk most of the time
292# causing a significant performance penality.
293# If the system has enough physical memory increasing the cache will improve the
294# performance by keeping more symbols in memory. Note that the value works on
295# a logarithmic scale so increasing the size by one will roughly double the
296# memory usage. The cache size is given by this formula:
297# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
298# corresponding to a cache size of 2^16 = 65536 symbols
299
300SYMBOL_CACHE_SIZE = 0
301
302#---------------------------------------------------------------------------
303# Build related configuration options
304#---------------------------------------------------------------------------
305
306# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
307# documentation are documented, even if no documentation was available.
308# Private class members and static file members will be hidden unless
309# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
310
311EXTRACT_ALL = NO
312
313# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
314# will be included in the documentation.
315
316EXTRACT_PRIVATE = NO
317
318# If the EXTRACT_STATIC tag is set to YES all static members of a file
319# will be included in the documentation.
320
321EXTRACT_STATIC = NO
322
323# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
324# defined locally in source files will be included in the documentation.
325# If set to NO only classes defined in header files are included.
326
327EXTRACT_LOCAL_CLASSES = YES
328
329# This flag is only useful for Objective-C code. When set to YES local
330# methods, which are defined in the implementation section but not in
331# the interface are included in the documentation.
332# If set to NO (the default) only methods in the interface are included.
333
334EXTRACT_LOCAL_METHODS = NO
335
336# If this flag is set to YES, the members of anonymous namespaces will be
337# extracted and appear in the documentation as a namespace called
338# 'anonymous_namespace{file}', where file will be replaced with the base
339# name of the file that contains the anonymous namespace. By default
340# anonymous namespaces are hidden.
341
342EXTRACT_ANON_NSPACES = NO
343
344# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
345# undocumented members of documented classes, files or namespaces.
346# If set to NO (the default) these members will be included in the
347# various overviews, but no documentation section is generated.
348# This option has no effect if EXTRACT_ALL is enabled.
349
350HIDE_UNDOC_MEMBERS = NO
351
352# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
353# undocumented classes that are normally visible in the class hierarchy.
354# If set to NO (the default) these classes will be included in the various
355# overviews. This option has no effect if EXTRACT_ALL is enabled.
356
357HIDE_UNDOC_CLASSES = NO
358
359# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
360# friend (class|struct|union) declarations.
361# If set to NO (the default) these declarations will be included in the
362# documentation.
363
364HIDE_FRIEND_COMPOUNDS = NO
365
366# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
367# documentation blocks found inside the body of a function.
368# If set to NO (the default) these blocks will be appended to the
369# function's detailed documentation block.
370
371HIDE_IN_BODY_DOCS = NO
372
373# The INTERNAL_DOCS tag determines if documentation
374# that is typed after a \internal command is included. If the tag is set
375# to NO (the default) then the documentation will be excluded.
376# Set it to YES to include the internal documentation.
377
378INTERNAL_DOCS = NO
379
380# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
381# file names in lower-case letters. If set to YES upper-case letters are also
382# allowed. This is useful if you have classes or files whose names only differ
383# in case and if your file system supports case sensitive file names. Windows
384# and Mac users are advised to set this option to NO.
385
386CASE_SENSE_NAMES = NO
387
388# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
389# will show members with their full class and namespace scopes in the
390# documentation. If set to YES the scope will be hidden.
391
392HIDE_SCOPE_NAMES = NO
393
394# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
395# will put a list of the files that are included by a file in the documentation
396# of that file.
397
398SHOW_INCLUDE_FILES = YES
399
400# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
401# will list include files with double quotes in the documentation
402# rather than with sharp brackets.
403
404FORCE_LOCAL_INCLUDES = NO
405
406# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
407# is inserted in the documentation for inline members.
408
409INLINE_INFO = YES
410
411# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
412# will sort the (detailed) documentation of file and class members
413# alphabetically by member name. If set to NO the members will appear in
414# declaration order.
415
416SORT_MEMBER_DOCS = YES
417
418# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
419# brief documentation of file, namespace and class members alphabetically
420# by member name. If set to NO (the default) the members will appear in
421# declaration order.
422
423SORT_BRIEF_DOCS = NO
424
425# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
426# will sort the (brief and detailed) documentation of class members so that
427# constructors and destructors are listed first. If set to NO (the default)
428# the constructors will appear in the respective orders defined by
429# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
430# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
431# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
432
433SORT_MEMBERS_CTORS_1ST = NO
434
435# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
436# hierarchy of group names into alphabetical order. If set to NO (the default)
437# the group names will appear in their defined order.
438
439SORT_GROUP_NAMES = NO
440
441# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
442# sorted by fully-qualified names, including namespaces. If set to
443# NO (the default), the class list will be sorted only by class name,
444# not including the namespace part.
445# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
446# Note: This option applies only to the class list, not to the
447# alphabetical list.
448
449SORT_BY_SCOPE_NAME = NO
450
451# The GENERATE_TODOLIST tag can be used to enable (YES) or
452# disable (NO) the todo list. This list is created by putting \todo
453# commands in the documentation.
454
455GENERATE_TODOLIST = YES
456
457# The GENERATE_TESTLIST tag can be used to enable (YES) or
458# disable (NO) the test list. This list is created by putting \test
459# commands in the documentation.
460
461GENERATE_TESTLIST = YES
462
463# The GENERATE_BUGLIST tag can be used to enable (YES) or
464# disable (NO) the bug list. This list is created by putting \bug
465# commands in the documentation.
466
467GENERATE_BUGLIST = YES
468
469# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
470# disable (NO) the deprecated list. This list is created by putting
471# \deprecated commands in the documentation.
472
473GENERATE_DEPRECATEDLIST= YES
474
475# The ENABLED_SECTIONS tag can be used to enable conditional
476# documentation sections, marked by \if sectionname ... \endif.
477
478ENABLED_SECTIONS =
479
480# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
481# the initial value of a variable or macro consists of for it to appear in
482# the documentation. If the initializer consists of more lines than specified
483# here it will be hidden. Use a value of 0 to hide initializers completely.
484# The appearance of the initializer of individual variables and macros in the
485# documentation can be controlled using \showinitializer or \hideinitializer
486# command in the documentation regardless of this setting.
487
488MAX_INITIALIZER_LINES = 30
489
490# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
491# at the bottom of the documentation of classes and structs. If set to YES the
492# list will mention the files that were used to generate the documentation.
493
494SHOW_USED_FILES = YES
495
496# If the sources in your project are distributed over multiple directories
497# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
498# in the documentation. The default is NO.
499
500SHOW_DIRECTORIES = NO
501
502# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
503# This will remove the Files entry from the Quick Index and from the
504# Folder Tree View (if specified). The default is YES.
505
506SHOW_FILES = YES
507
508# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
509# Namespaces page. This will remove the Namespaces entry from the Quick Index
510# and from the Folder Tree View (if specified). The default is YES.
511
512SHOW_NAMESPACES = YES
513
514# The FILE_VERSION_FILTER tag can be used to specify a program or script that
515# doxygen should invoke to get the current version for each file (typically from
516# the version control system). Doxygen will invoke the program by executing (via
517# popen()) the command <command> <input-file>, where <command> is the value of
518# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
519# provided by doxygen. Whatever the program writes to standard output
520# is used as the file version. See the manual for examples.
521
522FILE_VERSION_FILTER =
523
524# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
525# by doxygen. The layout file controls the global structure of the generated
526# output files in an output format independent way. The create the layout file
527# that represents doxygen's defaults, run doxygen with the -l option.
528# You can optionally specify a file name after the option, if omitted
529# DoxygenLayout.xml will be used as the name of the layout file.
530
531LAYOUT_FILE =
532
533#---------------------------------------------------------------------------
534# configuration options related to warning and progress messages
535#---------------------------------------------------------------------------
536
537# The QUIET tag can be used to turn on/off the messages that are generated
538# by doxygen. Possible values are YES and NO. If left blank NO is used.
539
540QUIET = NO
541
542# The WARNINGS tag can be used to turn on/off the warning messages that are
543# generated by doxygen. Possible values are YES and NO. If left blank
544# NO is used.
545
546WARNINGS = YES
547
548# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
549# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
550# automatically be disabled.
551
552WARN_IF_UNDOCUMENTED = YES
553
554# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
555# potential errors in the documentation, such as not documenting some
556# parameters in a documented function, or documenting parameters that
557# don't exist or using markup commands wrongly.
558
559WARN_IF_DOC_ERROR = YES
560
561# The WARN_NO_PARAMDOC option can be enabled to get warnings for
562# functions that are documented, but have no documentation for their parameters
563# or return value. If set to NO (the default) doxygen will only warn about
564# wrong or incomplete parameter documentation, but not about the absence of
565# documentation.
566
567WARN_NO_PARAMDOC = NO
568
569# The WARN_FORMAT tag determines the format of the warning messages that
570# doxygen can produce. The string should contain the $file, $line, and $text
571# tags, which will be replaced by the file and line number from which the
572# warning originated and the warning text. Optionally the format may contain
573# $version, which will be replaced by the version of the file (if it could
574# be obtained via FILE_VERSION_FILTER)
575
576WARN_FORMAT = "$file:$line: $text"
577
578# The WARN_LOGFILE tag can be used to specify a file to which warning
579# and error messages should be written. If left blank the output is written
580# to stderr.
581
582WARN_LOGFILE =
583
584#---------------------------------------------------------------------------
585# configuration options related to the input files
586#---------------------------------------------------------------------------
587
588# The INPUT tag can be used to specify the files and/or directories that contain
589# documented source files. You may enter file names like "myfile.cpp" or
590# directories like "/usr/src/myproject". Separate the files or directories
591# with spaces.
592
593INPUT = ../src/bin
594
595# This tag can be used to specify the character encoding of the source files
596# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
597# also the default input encoding. Doxygen uses libiconv (or the iconv built
598# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
599# the list of possible encodings.
600
601INPUT_ENCODING = UTF-8
602
603# If the value of the INPUT tag contains directories, you can use the
604# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
605# and *.h) to filter out the source-files in the directories. If left
606# blank the following patterns are tested:
607# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
608# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
609# *.f90 *.f *.vhd *.vhdl
610
611FILE_PATTERNS = *.c \
612 *.cc \
613 *.cxx \
614 *.cpp \
615 *.c++ \
616 *.d \
617 *.java \
618 *.ii \
619 *.ixx \
620 *.ipp \
621 *.i++ \
622 *.inl \
623 *.h \
624 *.hh \
625 *.hxx \
626 *.hpp \
627 *.h++ \
628 *.idl \
629 *.odl \
630 *.cs \
631 *.php \
632 *.php3 \
633 *.inc \
634 *.m \
635 *.mm \
636 *.dox \
637 *.py \
638 *.f90 \
639 *.f \
640 *.vhd \
641 *.vhdl
642
643# The RECURSIVE tag can be used to turn specify whether or not subdirectories
644# should be searched for input files as well. Possible values are YES and NO.
645# If left blank NO is used.
646
647RECURSIVE = YES
648
649# The EXCLUDE tag can be used to specify files and/or directories that should
650# excluded from the INPUT source files. This way you can easily exclude a
651# subdirectory from a directory tree whose root is specified with the INPUT tag.
652
653EXCLUDE =
654
655# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
656# directories that are symbolic links (a Unix filesystem feature) are excluded
657# from the input.
658
659EXCLUDE_SYMLINKS = NO
660
661# If the value of the INPUT tag contains directories, you can use the
662# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
663# certain files from those directories. Note that the wildcards are matched
664# against the file with absolute path, so to exclude all test directories
665# for example use the pattern */test/*
666
667EXCLUDE_PATTERNS =
668
669# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
670# (namespaces, classes, functions, etc.) that should be excluded from the
671# output. The symbol name can be a fully qualified name, a word, or if the
672# wildcard * is used, a substring. Examples: ANamespace, AClass,
673# AClass::ANamespace, ANamespace::*Test
674
675EXCLUDE_SYMBOLS =
676
677# The EXAMPLE_PATH tag can be used to specify one or more files or
678# directories that contain example code fragments that are included (see
679# the \include command).
680
681EXAMPLE_PATH =
682
683# If the value of the EXAMPLE_PATH tag contains directories, you can use the
684# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
685# and *.h) to filter out the source-files in the directories. If left
686# blank all files are included.
687
688EXAMPLE_PATTERNS = *
689
690# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
691# searched for input files to be used with the \include or \dontinclude
692# commands irrespective of the value of the RECURSIVE tag.
693# Possible values are YES and NO. If left blank NO is used.
694
695EXAMPLE_RECURSIVE = NO
696
697# The IMAGE_PATH tag can be used to specify one or more files or
698# directories that contain image that are included in the documentation (see
699# the \image command).
700
701IMAGE_PATH =
702
703# The INPUT_FILTER tag can be used to specify a program that doxygen should
704# invoke to filter for each input file. Doxygen will invoke the filter program
705# by executing (via popen()) the command <filter> <input-file>, where <filter>
706# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
707# input file. Doxygen will then use the output that the filter program writes
708# to standard output. If FILTER_PATTERNS is specified, this tag will be
709# ignored.
710
711INPUT_FILTER =
712
713# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
714# basis. Doxygen will compare the file name with each pattern and apply the
715# filter if there is a match. The filters are a list of the form:
716# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
717# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
718# is applied to all files.
719
720FILTER_PATTERNS =
721
722# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
723# INPUT_FILTER) will be used to filter the input files when producing source
724# files to browse (i.e. when SOURCE_BROWSER is set to YES).
725
726FILTER_SOURCE_FILES = NO
727
728#---------------------------------------------------------------------------
729# configuration options related to source browsing
730#---------------------------------------------------------------------------
731
732# If the SOURCE_BROWSER tag is set to YES then a list of source files will
733# be generated. Documented entities will be cross-referenced with these sources.
734# Note: To get rid of all source code in the generated output, make sure also
735# VERBATIM_HEADERS is set to NO.
736
737SOURCE_BROWSER = NO
738
739# Setting the INLINE_SOURCES tag to YES will include the body
740# of functions and classes directly in the documentation.
741
742INLINE_SOURCES = NO
743
744# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
745# doxygen to hide any special comment blocks from generated source code
746# fragments. Normal C and C++ comments will always remain visible.
747
748STRIP_CODE_COMMENTS = YES
749
750# If the REFERENCED_BY_RELATION tag is set to YES
751# then for each documented function all documented
752# functions referencing it will be listed.
753
754REFERENCED_BY_RELATION = NO
755
756# If the REFERENCES_RELATION tag is set to YES
757# then for each documented function all documented entities
758# called/used by that function will be listed.
759
760REFERENCES_RELATION = NO
761
762# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
763# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
764# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
765# link to the source code. Otherwise they will link to the documentation.
766
767REFERENCES_LINK_SOURCE = YES
768
769# If the USE_HTAGS tag is set to YES then the references to source code
770# will point to the HTML generated by the htags(1) tool instead of doxygen
771# built-in source browser. The htags tool is part of GNU's global source
772# tagging system (see http://www.gnu.org/software/global/global.html). You
773# will need version 4.8.6 or higher.
774
775USE_HTAGS = NO
776
777# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
778# will generate a verbatim copy of the header file for each class for
779# which an include is specified. Set to NO to disable this.
780
781VERBATIM_HEADERS = YES
782
783#---------------------------------------------------------------------------
784# configuration options related to the alphabetical class index
785#---------------------------------------------------------------------------
786
787# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
788# of all compounds will be generated. Enable this if the project
789# contains a lot of classes, structs, unions or interfaces.
790
791ALPHABETICAL_INDEX = YES
792
793# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
794# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
795# in which this list will be split (can be a number in the range [1..20])
796
797COLS_IN_ALPHA_INDEX = 5
798
799# In case all classes in a project start with a common prefix, all
800# classes will be put under the same header in the alphabetical index.
801# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
802# should be ignored while generating the index headers.
803
804IGNORE_PREFIX =
805
806#---------------------------------------------------------------------------
807# configuration options related to the HTML output
808#---------------------------------------------------------------------------
809
810# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
811# generate HTML output.
812
813GENERATE_HTML = YES
814
815# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
816# If a relative path is entered the value of OUTPUT_DIRECTORY will be
817# put in front of it. If left blank `html' will be used as the default path.
818
819HTML_OUTPUT = html
820
821# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
822# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
823# doxygen will generate files with .html extension.
824
825HTML_FILE_EXTENSION = .html
826
827# The HTML_HEADER tag can be used to specify a personal HTML header for
828# each generated HTML page. If it is left blank doxygen will generate a
829# standard header.
830
831HTML_HEADER =
832
833# The HTML_FOOTER tag can be used to specify a personal HTML footer for
834# each generated HTML page. If it is left blank doxygen will generate a
835# standard footer.
836
837HTML_FOOTER =
838
839# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
840# style sheet that is used by each HTML page. It can be used to
841# fine-tune the look of the HTML output. If the tag is left blank doxygen
842# will generate a default style sheet. Note that doxygen will try to copy
843# the style sheet file to the HTML output directory, so don't put your own
844# stylesheet in the HTML output directory as well, or it will be erased!
845
846HTML_STYLESHEET =
847
848# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
849# Doxygen will adjust the colors in the stylesheet and background images
850# according to this color. Hue is specified as an angle on a colorwheel,
851# see http://en.wikipedia.org/wiki/Hue for more information.
852# For instance the value 0 represents red, 60 is yellow, 120 is green,
853# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
854# The allowed range is 0 to 359.
855
856HTML_COLORSTYLE_HUE = 220
857
858# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
859# the colors in the HTML output. For a value of 0 the output will use
860# grayscales only. A value of 255 will produce the most vivid colors.
861
862HTML_COLORSTYLE_SAT = 100
863
864# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
865# the luminance component of the colors in the HTML output. Values below
866# 100 gradually make the output lighter, whereas values above 100 make
867# the output darker. The value divided by 100 is the actual gamma applied,
868# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
869# and 100 does not change the gamma.
870
871HTML_COLORSTYLE_GAMMA = 80
872
873# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
874# page will contain the date and time when the page was generated. Setting
875# this to NO can help when comparing the output of multiple runs.
876
877HTML_TIMESTAMP = YES
878
879# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
880# files or namespaces will be aligned in HTML using tables. If set to
881# NO a bullet list will be used.
882
883HTML_ALIGN_MEMBERS = YES
884
885# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
886# documentation will contain sections that can be hidden and shown after the
887# page has loaded. For this to work a browser that supports
888# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
889# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
890
891HTML_DYNAMIC_SECTIONS = NO
892
893# If the GENERATE_DOCSET tag is set to YES, additional index files
894# will be generated that can be used as input for Apple's Xcode 3
895# integrated development environment, introduced with OSX 10.5 (Leopard).
896# To create a documentation set, doxygen will generate a Makefile in the
897# HTML output directory. Running make will produce the docset in that
898# directory and running "make install" will install the docset in
899# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
900# it at startup.
901# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
902# for more information.
903
904GENERATE_DOCSET = NO
905
906# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
907# feed. A documentation feed provides an umbrella under which multiple
908# documentation sets from a single provider (such as a company or product suite)
909# can be grouped.
910
911DOCSET_FEEDNAME = "Doxygen generated docs"
912
913# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
914# should uniquely identify the documentation set bundle. This should be a
915# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
916# will append .docset to the name.
917
918DOCSET_BUNDLE_ID = org.doxygen.Project
919
920# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
921# the documentation publisher. This should be a reverse domain-name style
922# string, e.g. com.mycompany.MyDocSet.documentation.
923
924DOCSET_PUBLISHER_ID = org.doxygen.Publisher
925
926# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
927
928DOCSET_PUBLISHER_NAME = Publisher
929
930# If the GENERATE_HTMLHELP tag is set to YES, additional index files
931# will be generated that can be used as input for tools like the
932# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
933# of the generated HTML documentation.
934
935GENERATE_HTMLHELP = NO
936
937# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
938# be used to specify the file name of the resulting .chm file. You
939# can add a path in front of the file if the result should not be
940# written to the html output directory.
941
942CHM_FILE =
943
944# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
945# be used to specify the location (absolute path including file name) of
946# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
947# the HTML help compiler on the generated index.hhp.
948
949HHC_LOCATION =
950
951# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
952# controls if a separate .chi index file is generated (YES) or that
953# it should be included in the master .chm file (NO).
954
955GENERATE_CHI = NO
956
957# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
958# is used to encode HtmlHelp index (hhk), content (hhc) and project file
959# content.
960
961CHM_INDEX_ENCODING =
962
963# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
964# controls whether a binary table of contents is generated (YES) or a
965# normal table of contents (NO) in the .chm file.
966
967BINARY_TOC = NO
968
969# The TOC_EXPAND flag can be set to YES to add extra items for group members
970# to the contents of the HTML help documentation and to the tree view.
971
972TOC_EXPAND = NO
973
974# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
975# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
976# that can be used as input for Qt's qhelpgenerator to generate a
977# Qt Compressed Help (.qch) of the generated HTML documentation.
978
979GENERATE_QHP = NO
980
981# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
982# be used to specify the file name of the resulting .qch file.
983# The path specified is relative to the HTML output folder.
984
985QCH_FILE =
986
987# The QHP_NAMESPACE tag specifies the namespace to use when generating
988# Qt Help Project output. For more information please see
989# http://doc.trolltech.com/qthelpproject.html#namespace
990
991QHP_NAMESPACE = org.doxygen.Project
992
993# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
994# Qt Help Project output. For more information please see
995# http://doc.trolltech.com/qthelpproject.html#virtual-folders
996
997QHP_VIRTUAL_FOLDER = doc
998
999# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
1000# add. For more information please see
1001# http://doc.trolltech.com/qthelpproject.html#custom-filters
1002
1003QHP_CUST_FILTER_NAME =
1004
1005# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
1006# custom filter to add. For more information please see
1007# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
1008# Qt Help Project / Custom Filters</a>.
1009
1010QHP_CUST_FILTER_ATTRS =
1011
1012# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1013# project's
1014# filter section matches.
1015# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
1016# Qt Help Project / Filter Attributes</a>.
1017
1018QHP_SECT_FILTER_ATTRS =
1019
1020# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
1021# be used to specify the location of Qt's qhelpgenerator.
1022# If non-empty doxygen will try to run qhelpgenerator on the generated
1023# .qhp file.
1024
1025QHG_LOCATION =
1026
1027# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
1028# will be generated, which together with the HTML files, form an Eclipse help
1029# plugin. To install this plugin and make it available under the help contents
1030# menu in Eclipse, the contents of the directory containing the HTML and XML
1031# files needs to be copied into the plugins directory of eclipse. The name of
1032# the directory within the plugins directory should be the same as
1033# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
1034# the help appears.
1035
1036GENERATE_ECLIPSEHELP = NO
1037
1038# A unique identifier for the eclipse help plugin. When installing the plugin
1039# the directory name containing the HTML and XML files should also have
1040# this name.
1041
1042ECLIPSE_DOC_ID = org.doxygen.Project
1043
1044# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1045# top of each HTML page. The value NO (the default) enables the index and
1046# the value YES disables it.
1047
1048DISABLE_INDEX = NO
1049
1050# This tag can be used to set the number of enum values (range [0,1..20])
1051# that doxygen will group on one line in the generated HTML documentation.
1052# Note that a value of 0 will completely suppress the enum values from
1053# appearing in the overview section.
1054
1055ENUM_VALUES_PER_LINE = 4
1056
1057# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1058# structure should be generated to display hierarchical information.
1059# If the tag value is set to YES, a side panel will be generated
1060# containing a tree-like index structure (just like the one that
1061# is generated for HTML Help). For this to work a browser that supports
1062# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
1063# Windows users are probably better off using the HTML help feature.
1064
1065GENERATE_TREEVIEW = NO
1066
1067# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
1068# and Class Hierarchy pages using a tree view instead of an ordered list.
1069
1070USE_INLINE_TREES = NO
1071
1072# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1073# used to set the initial width (in pixels) of the frame in which the tree
1074# is shown.
1075
1076TREEVIEW_WIDTH = 250
1077
1078# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1079# links to external symbols imported via tag files in a separate window.
1080
1081EXT_LINKS_IN_WINDOW = NO
1082
1083# Use this tag to change the font size of Latex formulas included
1084# as images in the HTML documentation. The default is 10. Note that
1085# when you change the font size after a successful doxygen run you need
1086# to manually remove any form_*.png images from the HTML output directory
1087# to force them to be regenerated.
1088
1089FORMULA_FONTSIZE = 10
1090
1091# Use the FORMULA_TRANPARENT tag to determine whether or not the images
1092# generated for formulas are transparent PNGs. Transparent PNGs are
1093# not supported properly for IE 6.0, but are supported on all modern browsers.
1094# Note that when changing this option you need to delete any form_*.png files
1095# in the HTML output before the changes have effect.
1096
1097FORMULA_TRANSPARENT = YES
1098
1099# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
1100# (see http://www.mathjax.org) which uses client side Javascript for the
1101# rendering instead of using prerendered bitmaps. Use this if you do not
1102# have LaTeX installed or if you want to formulas look prettier in the HTML
1103# output. When enabled you also need to install MathJax separately and
1104# configure the path to it using the MATHJAX_RELPATH option.
1105
1106USE_MATHJAX = NO
1107
1108# When MathJax is enabled you need to specify the location relative to the
1109# HTML output directory using the MATHJAX_RELPATH option. The destination
1110# directory should contain the MathJax.js script. For instance, if the mathjax
1111# directory is located at the same level as the HTML output directory, then
1112# MATHJAX_RELPATH should be ../mathjax. The default value points to the
1113# mathjax.org site, so you can quickly see the result without installing
1114# MathJax, but it is strongly recommended to install a local copy of MathJax
1115# before deployment.
1116
1117MATHJAX_RELPATH = http://www.mathjax.org/mathjax
1118
1119# When the SEARCHENGINE tag is enabled doxygen will generate a search box
1120# for the HTML output. The underlying search engine uses javascript
1121# and DHTML and should work on any modern browser. Note that when using
1122# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
1123# (GENERATE_DOCSET) there is already a search function so this one should
1124# typically be disabled. For large projects the javascript based search engine
1125# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1126
1127SEARCHENGINE = YES
1128
1129# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1130# implemented using a PHP enabled web server instead of at the web client
1131# using Javascript. Doxygen will generate the search PHP script and index
1132# file to put on the web server. The advantage of the server
1133# based approach is that it scales better to large projects and allows
1134# full text search. The disadvantages are that it is more difficult to setup
1135# and does not have live searching capabilities.
1136
1137SERVER_BASED_SEARCH = NO
1138
1139#---------------------------------------------------------------------------
1140# configuration options related to the LaTeX output
1141#---------------------------------------------------------------------------
1142
1143# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1144# generate Latex output.
1145
1146GENERATE_LATEX = YES
1147
1148# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1149# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1150# put in front of it. If left blank `latex' will be used as the default path.
1151
1152LATEX_OUTPUT = latex
1153
1154# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1155# invoked. If left blank `latex' will be used as the default command name.
1156# Note that when enabling USE_PDFLATEX this option is only used for
1157# generating bitmaps for formulas in the HTML output, but not in the
1158# Makefile that is written to the output directory.
1159
1160LATEX_CMD_NAME = latex
1161
1162# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1163# generate index for LaTeX. If left blank `makeindex' will be used as the
1164# default command name.
1165
1166MAKEINDEX_CMD_NAME = makeindex
1167
1168# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1169# LaTeX documents. This may be useful for small projects and may help to
1170# save some trees in general.
1171
1172COMPACT_LATEX = NO
1173
1174# The PAPER_TYPE tag can be used to set the paper type that is used
1175# by the printer. Possible values are: a4, letter, legal and
1176# executive. If left blank a4wide will be used.
1177
1178PAPER_TYPE = a4
1179
1180# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1181# packages that should be included in the LaTeX output.
1182
1183EXTRA_PACKAGES =
1184
1185# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1186# the generated latex document. The header should contain everything until
1187# the first chapter. If it is left blank doxygen will generate a
1188# standard header. Notice: only use this tag if you know what you are doing!
1189
1190LATEX_HEADER =
1191
1192# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1193# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1194# contain links (just like the HTML output) instead of page references
1195# This makes the output suitable for online browsing using a pdf viewer.
1196
1197PDF_HYPERLINKS = YES
1198
1199# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1200# plain latex in the generated Makefile. Set this option to YES to get a
1201# higher quality PDF documentation.
1202
1203USE_PDFLATEX = YES
1204
1205# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1206# command to the generated LaTeX files. This will instruct LaTeX to keep
1207# running if errors occur, instead of asking the user for help.
1208# This option is also used when generating formulas in HTML.
1209
1210LATEX_BATCHMODE = NO
1211
1212# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1213# include the index chapters (such as File Index, Compound Index, etc.)
1214# in the output.
1215
1216LATEX_HIDE_INDICES = NO
1217
1218# If LATEX_SOURCE_CODE is set to YES then doxygen will include
1219# source code with syntax highlighting in the LaTeX output.
1220# Note that which sources are shown also depends on other settings
1221# such as SOURCE_BROWSER.
1222
1223LATEX_SOURCE_CODE = NO
1224
1225#---------------------------------------------------------------------------
1226# configuration options related to the RTF output
1227#---------------------------------------------------------------------------
1228
1229# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1230# The RTF output is optimized for Word 97 and may not look very pretty with
1231# other RTF readers or editors.
1232
1233GENERATE_RTF = NO
1234
1235# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1236# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1237# put in front of it. If left blank `rtf' will be used as the default path.
1238
1239RTF_OUTPUT = rtf
1240
1241# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1242# RTF documents. This may be useful for small projects and may help to
1243# save some trees in general.
1244
1245COMPACT_RTF = NO
1246
1247# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1248# will contain hyperlink fields. The RTF file will
1249# contain links (just like the HTML output) instead of page references.
1250# This makes the output suitable for online browsing using WORD or other
1251# programs which support those fields.
1252# Note: wordpad (write) and others do not support links.
1253
1254RTF_HYPERLINKS = NO
1255
1256# Load stylesheet definitions from file. Syntax is similar to doxygen's
1257# config file, i.e. a series of assignments. You only have to provide
1258# replacements, missing definitions are set to their default value.
1259
1260RTF_STYLESHEET_FILE =
1261
1262# Set optional variables used in the generation of an rtf document.
1263# Syntax is similar to doxygen's config file.
1264
1265RTF_EXTENSIONS_FILE =
1266
1267#---------------------------------------------------------------------------
1268# configuration options related to the man page output
1269#---------------------------------------------------------------------------
1270
1271# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1272# generate man pages
1273
1274GENERATE_MAN = NO
1275
1276# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1277# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1278# put in front of it. If left blank `man' will be used as the default path.
1279
1280MAN_OUTPUT = man
1281
1282# The MAN_EXTENSION tag determines the extension that is added to
1283# the generated man pages (default is the subroutine's section .3)
1284
1285MAN_EXTENSION = .3
1286
1287# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1288# then it will generate one additional man file for each entity
1289# documented in the real man page(s). These additional files
1290# only source the real man page, but without them the man command
1291# would be unable to find the correct page. The default is NO.
1292
1293MAN_LINKS = NO
1294
1295#---------------------------------------------------------------------------
1296# configuration options related to the XML output
1297#---------------------------------------------------------------------------
1298
1299# If the GENERATE_XML tag is set to YES Doxygen will
1300# generate an XML file that captures the structure of
1301# the code including all documentation.
1302
1303GENERATE_XML = NO
1304
1305# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1306# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1307# put in front of it. If left blank `xml' will be used as the default path.
1308
1309XML_OUTPUT = xml
1310
1311# The XML_SCHEMA tag can be used to specify an XML schema,
1312# which can be used by a validating XML parser to check the
1313# syntax of the XML files.
1314
1315XML_SCHEMA =
1316
1317# The XML_DTD tag can be used to specify an XML DTD,
1318# which can be used by a validating XML parser to check the
1319# syntax of the XML files.
1320
1321XML_DTD =
1322
1323# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1324# dump the program listings (including syntax highlighting
1325# and cross-referencing information) to the XML output. Note that
1326# enabling this will significantly increase the size of the XML output.
1327
1328XML_PROGRAMLISTING = YES
1329
1330#---------------------------------------------------------------------------
1331# configuration options for the AutoGen Definitions output
1332#---------------------------------------------------------------------------
1333
1334# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1335# generate an AutoGen Definitions (see autogen.sf.net) file
1336# that captures the structure of the code including all
1337# documentation. Note that this feature is still experimental
1338# and incomplete at the moment.
1339
1340GENERATE_AUTOGEN_DEF = NO
1341
1342#---------------------------------------------------------------------------
1343# configuration options related to the Perl module output
1344#---------------------------------------------------------------------------
1345
1346# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1347# generate a Perl module file that captures the structure of
1348# the code including all documentation. Note that this
1349# feature is still experimental and incomplete at the
1350# moment.
1351
1352GENERATE_PERLMOD = NO
1353
1354# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1355# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1356# to generate PDF and DVI output from the Perl module output.
1357
1358PERLMOD_LATEX = NO
1359
1360# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1361# nicely formatted so it can be parsed by a human reader. This is useful
1362# if you want to understand what is going on. On the other hand, if this
1363# tag is set to NO the size of the Perl module output will be much smaller
1364# and Perl will parse it just the same.
1365
1366PERLMOD_PRETTY = YES
1367
1368# The names of the make variables in the generated doxyrules.make file
1369# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1370# This is useful so different doxyrules.make files included by the same
1371# Makefile don't overwrite each other's variables.
1372
1373PERLMOD_MAKEVAR_PREFIX =
1374
1375#---------------------------------------------------------------------------
1376# Configuration options related to the preprocessor
1377#---------------------------------------------------------------------------
1378
1379# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1380# evaluate all C-preprocessor directives found in the sources and include
1381# files.
1382
1383ENABLE_PREPROCESSING = YES
1384
1385# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1386# names in the source code. If set to NO (the default) only conditional
1387# compilation will be performed. Macro expansion can be done in a controlled
1388# way by setting EXPAND_ONLY_PREDEF to YES.
1389
1390MACRO_EXPANSION = NO
1391
1392# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1393# then the macro expansion is limited to the macros specified with the
1394# PREDEFINED and EXPAND_AS_DEFINED tags.
1395
1396EXPAND_ONLY_PREDEF = NO
1397
1398# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1399# in the INCLUDE_PATH (see below) will be search if a #include is found.
1400
1401SEARCH_INCLUDES = YES
1402
1403# The INCLUDE_PATH tag can be used to specify one or more directories that
1404# contain include files that are not input files but should be processed by
1405# the preprocessor.
1406
1407INCLUDE_PATH =
1408
1409# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1410# patterns (like *.h and *.hpp) to filter out the header-files in the
1411# directories. If left blank, the patterns specified with FILE_PATTERNS will
1412# be used.
1413
1414INCLUDE_FILE_PATTERNS =
1415
1416# The PREDEFINED tag can be used to specify one or more macro names that
1417# are defined before the preprocessor is started (similar to the -D option of
1418# gcc). The argument of the tag is a list of macros of the form: name
1419# or name=definition (no spaces). If the definition and the = are
1420# omitted =1 is assumed. To prevent a macro definition from being
1421# undefined via #undef or recursively expanded use the := operator
1422# instead of the = operator.
1423
1424PREDEFINED =
1425
1426# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1427# this tag can be used to specify a list of macro names that should be expanded.
1428# The macro definition that is found in the sources will be used.
1429# Use the PREDEFINED tag if you want to use a different macro definition.
1430
1431EXPAND_AS_DEFINED =
1432
1433# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1434# doxygen's preprocessor will remove all function-like macros that are alone
1435# on a line, have an all uppercase name, and do not end with a semicolon. Such
1436# function macros are typically used for boiler-plate code, and will confuse
1437# the parser if not removed.
1438
1439SKIP_FUNCTION_MACROS = YES
1440
1441#---------------------------------------------------------------------------
1442# Configuration::additions related to external references
1443#---------------------------------------------------------------------------
1444
1445# The TAGFILES option can be used to specify one or more tagfiles.
1446# Optionally an initial location of the external documentation
1447# can be added for each tagfile. The format of a tag file without
1448# this location is as follows:
1449# TAGFILES = file1 file2 ...
1450# Adding location for the tag files is done as follows:
1451# TAGFILES = file1=loc1 "file2 = loc2" ...
1452# where "loc1" and "loc2" can be relative or absolute paths or
1453# URLs. If a location is present for each tag, the installdox tool
1454# does not have to be run to correct the links.
1455# Note that each tag file must have a unique name
1456# (where the name does NOT include the path)
1457# If a tag file is not located in the directory in which doxygen
1458# is run, you must also specify the path to the tagfile here.
1459
1460TAGFILES =
1461
1462# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1463# a tag file that is based on the input files it reads.
1464
1465GENERATE_TAGFILE =
1466
1467# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1468# in the class index. If set to NO only the inherited external classes
1469# will be listed.
1470
1471ALLEXTERNALS = NO
1472
1473# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1474# in the modules index. If set to NO, only the current project's groups will
1475# be listed.
1476
1477EXTERNAL_GROUPS = YES
1478
1479# The PERL_PATH should be the absolute path and name of the perl script
1480# interpreter (i.e. the result of `which perl').
1481
1482PERL_PATH = /usr/bin/perl
1483
1484#---------------------------------------------------------------------------
1485# Configuration options related to the dot tool
1486#---------------------------------------------------------------------------
1487
1488# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1489# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1490# or super classes. Setting the tag to NO turns the diagrams off. Note that
1491# this option also works with HAVE_DOT disabled, but it is recommended to
1492# install and use dot, since it yields more powerful graphs.
1493
1494CLASS_DIAGRAMS = YES
1495
1496# You can define message sequence charts within doxygen comments using the \msc
1497# command. Doxygen will then run the mscgen tool (see
1498# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1499# documentation. The MSCGEN_PATH tag allows you to specify the directory where
1500# the mscgen tool resides. If left empty the tool is assumed to be found in the
1501# default search path.
1502
1503MSCGEN_PATH =
1504
1505# If set to YES, the inheritance and collaboration graphs will hide
1506# inheritance and usage relations if the target is undocumented
1507# or is not a class.
1508
1509HIDE_UNDOC_RELATIONS = YES
1510
1511# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1512# available from the path. This tool is part of Graphviz, a graph visualization
1513# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1514# have no effect if this option is set to NO (the default)
1515
1516HAVE_DOT = NO
1517
1518# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
1519# allowed to run in parallel. When set to 0 (the default) doxygen will
1520# base this on the number of processors available in the system. You can set it
1521# explicitly to a value larger than 0 to get control over the balance
1522# between CPU load and processing speed.
1523
1524DOT_NUM_THREADS = 0
1525
1526# By default doxygen will write a font called FreeSans.ttf to the output
1527# directory and reference it in all dot files that doxygen generates. This
1528# font does not include all possible unicode characters however, so when you need
1529# these (or just want a differently looking font) you can specify the font name
1530# using DOT_FONTNAME. You need need to make sure dot is able to find the font,
1531# which can be done by putting it in a standard location or by setting the
1532# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1533# containing the font.
1534
1535DOT_FONTNAME = FreeSans.ttf
1536
1537# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1538# The default size is 10pt.
1539
1540DOT_FONTSIZE = 10
1541
1542# By default doxygen will tell dot to use the output directory to look for the
1543# FreeSans.ttf font (which doxygen will put there itself). If you specify a
1544# different font using DOT_FONTNAME you can set the path where dot
1545# can find it using this tag.
1546
1547DOT_FONTPATH =
1548
1549# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1550# will generate a graph for each documented class showing the direct and
1551# indirect inheritance relations. Setting this tag to YES will force the
1552# the CLASS_DIAGRAMS tag to NO.
1553
1554CLASS_GRAPH = YES
1555
1556# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1557# will generate a graph for each documented class showing the direct and
1558# indirect implementation dependencies (inheritance, containment, and
1559# class references variables) of the class with other documented classes.
1560
1561COLLABORATION_GRAPH = YES
1562
1563# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1564# will generate a graph for groups, showing the direct groups dependencies
1565
1566GROUP_GRAPHS = YES
1567
1568# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1569# collaboration diagrams in a style similar to the OMG's Unified Modeling
1570# Language.
1571
1572UML_LOOK = NO
1573
1574# If set to YES, the inheritance and collaboration graphs will show the
1575# relations between templates and their instances.
1576
1577TEMPLATE_RELATIONS = NO
1578
1579# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1580# tags are set to YES then doxygen will generate a graph for each documented
1581# file showing the direct and indirect include dependencies of the file with
1582# other documented files.
1583
1584INCLUDE_GRAPH = YES
1585
1586# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1587# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1588# documented header file showing the documented files that directly or
1589# indirectly include this file.
1590
1591INCLUDED_BY_GRAPH = YES
1592
1593# If the CALL_GRAPH and HAVE_DOT options are set to YES then
1594# doxygen will generate a call dependency graph for every global function
1595# or class method. Note that enabling this option will significantly increase
1596# the time of a run. So in most cases it will be better to enable call graphs
1597# for selected functions only using the \callgraph command.
1598
1599CALL_GRAPH = NO
1600
1601# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1602# doxygen will generate a caller dependency graph for every global function
1603# or class method. Note that enabling this option will significantly increase
1604# the time of a run. So in most cases it will be better to enable caller
1605# graphs for selected functions only using the \callergraph command.
1606
1607CALLER_GRAPH = NO
1608
1609# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1610# will generate a graphical hierarchy of all classes instead of a textual one.
1611
1612GRAPHICAL_HIERARCHY = YES
1613
1614# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1615# then doxygen will show the dependencies a directory has on other directories
1616# in a graphical way. The dependency relations are determined by the #include
1617# relations between the files in the directories.
1618
1619DIRECTORY_GRAPH = YES
1620
1621# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1622# generated by dot. Possible values are png, jpg, or gif.
1623# If left blank png will be used.
1624
1625DOT_IMAGE_FORMAT = png
1626
1627# The tag DOT_PATH can be used to specify the path where the dot tool can be
1628# found. If left blank, it is assumed the dot tool can be found in the path.
1629
1630DOT_PATH =
1631
1632# The DOTFILE_DIRS tag can be used to specify one or more directories that
1633# contain dot files that are included in the documentation (see the
1634# \dotfile command).
1635
1636DOTFILE_DIRS =
1637
1638# The MSCFILE_DIRS tag can be used to specify one or more directories that
1639# contain msc files that are included in the documentation (see the
1640# \mscfile command).
1641
1642MSCFILE_DIRS =
1643
1644# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1645# nodes that will be shown in the graph. If the number of nodes in a graph
1646# becomes larger than this value, doxygen will truncate the graph, which is
1647# visualized by representing a node as a red box. Note that doxygen if the
1648# number of direct children of the root node in a graph is already larger than
1649# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1650# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1651
1652DOT_GRAPH_MAX_NODES = 50
1653
1654# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1655# graphs generated by dot. A depth value of 3 means that only nodes reachable
1656# from the root by following a path via at most 3 edges will be shown. Nodes
1657# that lay further from the root node will be omitted. Note that setting this
1658# option to 1 or 2 may greatly reduce the computation time needed for large
1659# code bases. Also note that the size of a graph can be further restricted by
1660# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1661
1662MAX_DOT_GRAPH_DEPTH = 0
1663
1664# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1665# background. This is disabled by default, because dot on Windows does not
1666# seem to support this out of the box. Warning: Depending on the platform used,
1667# enabling this option may lead to badly anti-aliased labels on the edges of
1668# a graph (i.e. they become hard to read).
1669
1670DOT_TRANSPARENT = NO
1671
1672# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1673# files in one run (i.e. multiple -o and -T options on the command line). This
1674# makes dot run faster, but since only newer versions of dot (>1.8.10)
1675# support this, this feature is disabled by default.
1676
1677DOT_MULTI_TARGETS = NO
1678
1679# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1680# generate a legend page explaining the meaning of the various boxes and
1681# arrows in the dot generated graphs.
1682
1683GENERATE_LEGEND = YES
1684
1685# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1686# remove the intermediate dot files that are used to generate
1687# the various graphs.
1688
1689DOT_CLEANUP = YES
diff --git a/doc/Makefile.am b/doc/Makefile.am
new file mode 100644
index 0000000..08cfea4
--- /dev/null
+++ b/doc/Makefile.am
@@ -0,0 +1,23 @@
1MAINTAINERCLEANFILES = Makefile.in
2
3.PHONY: doc
4
5PACKAGE_DOCNAME = $(PACKAGE_TARNAME)-$(PACKAGE_VERSION)-doc
6
7doc-clean:
8 rm -rf html/ latex/ $(PACKAGE_DOCNAME).tar*
9
10doc: all
11 doxygen
12 cp img/* html/
13 rm -rf $(PACKAGE_DOCNAME).tar*
14 mkdir -p $(PACKAGE_DOCNAME)/doc
15 cp -R html/ latex/ $(PACKAGE_DOCNAME)/doc
16 tar cf $(PACKAGE_DOCNAME).tar $(PACKAGE_DOCNAME)/
17 bzip2 -9 $(PACKAGE_DOCNAME).tar
18 rm -rf $(PACKAGE_DOCNAME)/
19 mv $(PACKAGE_DOCNAME).tar.bz2 $(top_srcdir)
20
21clean-local: doc-clean
22
23EXTRA_DIST = Doxyfile $(wildcard img/*.*) style.css head.html foot.html
diff --git a/doc/gimp/intro.xcf b/doc/gimp/intro.xcf
new file mode 100644
index 0000000..a1ca69e
--- /dev/null
+++ b/doc/gimp/intro.xcf
Binary files differ
diff --git a/doc/img/intro.png b/doc/img/intro.png
new file mode 100644
index 0000000..4aea29c
--- /dev/null
+++ b/doc/img/intro.png
Binary files differ
diff --git a/rules/auth_failed b/rules/auth_failed
new file mode 100644
index 0000000..ad802ea
--- /dev/null
+++ b/rules/auth_failed
@@ -0,0 +1,4 @@
1# This rules will match any log message that contains "Failed password for"
2# And add the tag "auth_fail" to it when indexing it into ES
3message = .*Failed password for.*
4tags = auth_fail
diff --git a/rules/auth_success b/rules/auth_success
new file mode 100644
index 0000000..6df9ceb
--- /dev/null
+++ b/rules/auth_success
@@ -0,0 +1,4 @@
1# This rules will match any log message that contains "Accepted password"
2# And add the tag "auth_success" to it when indexing it into ES
3message = .*Accepted password.*
4tags = auth_success
diff --git a/rules/tags_test b/rules/tags_test
new file mode 100644
index 0000000..f3d17ff
--- /dev/null
+++ b/rules/tags_test
@@ -0,0 +1,3 @@
1# This rules will match any log file in /var/log/ to add the tag "test2"
2filename = /var/log/*.log
3tags = test2
diff --git a/rules/watch_alllog b/rules/watch_alllog
new file mode 100644
index 0000000..958dfcf
--- /dev/null
+++ b/rules/watch_alllog
@@ -0,0 +1,3 @@
1# This rules will match any log file in /var/log/ to add the tag "syslog"
2filename = /var/log/*.log
3tags = syslog
diff --git a/rules/watch_httpd b/rules/watch_httpd
new file mode 100644
index 0000000..c59e09d
--- /dev/null
+++ b/rules/watch_httpd
@@ -0,0 +1,3 @@
1# This rules will match any apache log file in /var/log/httpd/ to add the tag "httpd"
2filename = /var/log/httpd/*_log
3tags = httpd
diff --git a/src/Makefile.am b/src/Makefile.am
new file mode 100644
index 0000000..addf4ca
--- /dev/null
+++ b/src/Makefile.am
@@ -0,0 +1,4 @@
1MAINTAINERCLEANFILES = Makefile.in
2
3SUBDIRS = bin
4
diff --git a/src/bin/Makefile.am b/src/bin/Makefile.am
new file mode 100644
index 0000000..777e147
--- /dev/null
+++ b/src/bin/Makefile.am
@@ -0,0 +1,8 @@
1MAINTAINERCLEANFILES = Makefile.in
2
3bin_PROGRAMS = smman
4
5smman_SOURCES = main.c rules.c spy.c logfiles.c send.c date.c conf.c logmessages.c libconf.c
6
7smman_LDFLAGS = @eina_LIBS@ @ecore_LIBS@ @libcurl_LIBS@
8smman_CPPFLAGS = -W -Wall -O2 -g @eina_CFLAGS@ @ecore_CFLAGS@ @libcurl_CFLAGS@ -DREVISION=\"@revision_number@\" -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS
diff --git a/src/bin/conf.c b/src/bin/conf.c
new file mode 100644
index 0000000..e3f0e43
--- /dev/null
+++ b/src/bin/conf.c
@@ -0,0 +1,94 @@
1/*
2 * Copyright © 2011 ASP64 <guillaume.friloux@asp64.com>
3 *
4 * This program is free software: you can redistribute it and/or modify
5 * it under the terms of the GNU General Public License as published by
6 * the Free Software Foundation, either version 3 of the License, or
7 * (at your option) any later version.
8 *
9 * This program is distributed in the hope that it will be useful,
10 * but WITHOUT ANY WARRANTY; without even the implied warranty of
11 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 * GNU General Public License for more details.
13 *
14 * You should have received a copy of the GNU General Public License
15 * along with this program. If not, see <http://www.gnu.org/licenses/>.
16 *
17 */
18
19/**
20 * @file conf.c
21 * @brief Manages configuration loading
22 * @author Guillaume Friloux <guillaume.friloux@asp64.com>
23 * @version 1.0
24 *
25 * Manages configuration loading
26 */
27#include "conf.h"
28
29/**
30 * @fn int conf_load(void)
31 * @brief This function will init libconf and ask to load our configuration
32 * file
33 *
34 * @return 0
35 */
36int conf_load(void)
37{
38 struct libconfig myconf;
39
40 strcpy(global_ESserver, "http://192.168.2.84:9200/logstash/events/");
41 strcpy(global_rulesdir, "/etc/smman/rules.d/");
42 strcpy(global_conf, "/etc/smman/smman.conf");
43 strcpy(global_type, "syslog");
44 gethostname(global_host, sizeof(global_host));
45
46 einadom_rules = eina_log_domain_register("smman_rules" , EINA_COLOR_LIGHTRED);
47 einadom_spy = eina_log_domain_register("smman_spy" , EINA_COLOR_LIGHTRED);
48 einadom_logfiles = eina_log_domain_register("smman_logfiles", EINA_COLOR_LIGHTRED);
49 einadom_send = eina_log_domain_register("smman_send" , EINA_COLOR_LIGHTRED);
50 einadom_conf = eina_log_domain_register("smman_conf" , EINA_COLOR_LIGHTRED);
51
52 libconfig_init(global_conf, &myconf);
53 libconfig_load(&myconf);
54
55 libconfig_list(&myconf, conf_load_var);
56
57 libconfig_free(&myconf);
58 return(0);
59}
60
61/**
62 * @fn int conf_load_var(char *variable, char *value)
63 * @brief This function is a callback for libconf, and receives a variable +
64 * its value found in a configuration file
65 *
66 * @param variable (char *) Variable's name
67 * @param value (char *) Variable's value
68 *
69 * @return 0
70 */
71int conf_load_var(char *variable, char *value)
72{
73 if( !strcmp(variable, "server") )
74 {
75 EINA_LOG_DOM_DBG(einadom_conf, "Setting ES server to %s", variable);
76 strcpy(global_ESserver, value);
77 }
78 else if( !strcmp(variable, "host") )
79 {
80 EINA_LOG_DOM_DBG(einadom_conf, "Setting default hostname to %s", variable);
81 strcpy(global_host, value);
82 }
83 else if( !strcmp(variable, "type") )
84 {
85 EINA_LOG_DOM_DBG(einadom_conf, "Setting default type to %s", variable);
86 strcpy(global_type, value);
87 }
88 else
89 {
90 EINA_LOG_DOM_ERR(einadom_conf, "Unknown config variable %s", variable);
91 }
92
93 return(0);
94}
diff --git a/src/bin/conf.h b/src/bin/conf.h
new file mode 100644
index 0000000..cca8743
--- /dev/null
+++ b/src/bin/conf.h
@@ -0,0 +1,33 @@
1/*
2 * Copyright © 2011 ASP64 <guillaume.friloux@asp64.com>
3 *
4 * This program is free software: you can redistribute it and/or modify
5 * it under the terms of the GNU General Public License as published by
6 * the Free Software Foundation, either version 3 of the License, or
7 * (at your option) any later version.
8 *
9 * This program is distributed in the hope that it will be useful,
10 * but WITHOUT ANY WARRANTY; without even the implied warranty of
11 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 * GNU General Public License for more details.
13 *
14 * You should have received a copy of the GNU General Public License
15 * along with this program. If not, see <http://www.gnu.org/licenses/>.
16 *
17 */
18
19/**
20 * @file conf.h
21 * @brief Contains all includes and prototypes for conf.c
22 * @author Guillaume Friloux <guillaume.friloux@asp64.com>
23 * @version 1.0
24 *
25 * Contains all includes and prototypes for conf.c
26 */
27#include <unistd.h>
28
29#include "libconf.h"
30#include "global.h"
31
32int conf_load(void);
33int conf_load_var(char *variable, char *value);
diff --git a/src/bin/date.c b/src/bin/date.c
new file mode 100644
index 0000000..e39af8a
--- /dev/null
+++ b/src/bin/date.c
@@ -0,0 +1,47 @@
1/*
2 * Copyright © 2011 ASP64 <guillaume.friloux@asp64.com>
3 *
4 * This program is free software: you can redistribute it and/or modify
5 * it under the terms of the GNU General Public License as published by
6 * the Free Software Foundation, either version 3 of the License, or
7 * (at your option) any later version.
8 *
9 * This program is distributed in the hope that it will be useful,
10 * but WITHOUT ANY WARRANTY; without even the implied warranty of
11 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 * GNU General Public License for more details.
13 *
14 * You should have received a copy of the GNU General Public License
15 * along with this program. If not, see <http://www.gnu.org/licenses/>.
16 *
17 */
18
19/**
20 * @file date.c
21 * @brief Gets us the current date, like logstash does
22 * @author Guillaume Friloux <guillaume.friloux@asp64.com>
23 * @version 1.0
24 *
25 * Gets us the current date, like logstash does
26 */
27
28#include "date.h"
29
30/**
31 * @fn char * timestamp_XML(char * date)
32 * @brief Gets us the current date, like logstash does
33 * @bug it doesnt get us date in UTC format, it gets us date on the system
34 *
35 * @param date (char *) Buffer where we will store the date
36 *
37 * @return 0
38 */
39char * timestamp_XML(char * date)
40{
41 time_t temps;
42 struct tm temp;
43 temps=time(NULL);
44 localtime_r(&temps,&temp);
45 sprintf(date,"%04d-%02d-%02dT%02d:%02d:%02d.000000Z",(temp.tm_year)+1900,(temp.tm_mon)+1,temp.tm_mday,temp.tm_hour,temp.tm_min,temp.tm_sec);
46 return(date);
47}
diff --git a/src/bin/date.h b/src/bin/date.h
new file mode 100644
index 0000000..64cc339
--- /dev/null
+++ b/src/bin/date.h
@@ -0,0 +1,31 @@
1/*
2 * Copyright © 2011 ASP64 <guillaume.friloux@asp64.com>
3 *
4 * This program is free software: you can redistribute it and/or modify
5 * it under the terms of the GNU General Public License as published by
6 * the Free Software Foundation, either version 3 of the License, or
7 * (at your option) any later version.
8 *
9 * This program is distributed in the hope that it will be useful,
10 * but WITHOUT ANY WARRANTY; without even the implied warranty of
11 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 * GNU General Public License for more details.
13 *
14 * You should have received a copy of the GNU General Public License
15 * along with this program. If not, see <http://www.gnu.org/licenses/>.
16 *
17 */
18
19/**
20 * @file date.h
21 * @brief Contains all includes and prototypes for date.c
22 * @author Guillaume Friloux <guillaume.friloux@asp64.com>
23 * @version 1.0
24 *
25 * Contains all includes and prototypes for date.c
26 */
27#include <time.h>
28#include <stdio.h>
29
30char * timestamp_XML(char * date);
31
diff --git a/src/bin/global.h b/src/bin/global.h
new file mode 100644
index 0000000..7728d68
--- /dev/null
+++ b/src/bin/global.h
@@ -0,0 +1,96 @@
1/*
2 * Copyright © 2011 ASP64 <guillaume.friloux@asp64.com>
3 *
4 * This program is free software: you can redistribute it and/or modify
5 * it under the terms of the GNU General Public License as published by
6 * the Free Software Foundation, either version 3 of the License, or
7 * (at your option) any later version.
8 *
9 * This program is distributed in the hope that it will be useful,
10 * but WITHOUT ANY WARRANTY; without even the implied warranty of
11 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 * GNU General Public License for more details.
13 *
14 * You should have received a copy of the GNU General Public License
15 * along with this program. If not, see <http://www.gnu.org/licenses/>.
16 *
17 */
18
19/**
20 * @file global.h
21 * @brief Contains all global variables we need
22 * @author Guillaume Friloux <guillaume.friloux@asp64.com>
23 * @version 1.0
24 * @todo It could be improved because not all structs are used everywhere.
25 *
26 * Contains all global variables we need
27 */
28#include <Eina.h>
29#include <Ecore.h>
30#include <Ecore_File.h>
31
32#ifndef GLOBALVARS
33#define GLOBALVARS
34char global_rulesdir[35], /**< Allows us to store the rules directory */
35 global_conf[35], /**< Allows us to store the configuration directory */
36 global_host[35], /**< Allows us to store the default hostname */
37 global_type[35], /**< Allows us to store the default type */
38 global_ESserver[128]; /**< Allows us to store ElasticSearch server adress */
39
40/**
41 * @struct rule
42 * @brief This structure can handle a rule described in the rule directory
43 */
44struct rule
45{
46 char *name, /**< Rule's name (Guessed using the filename of the rule inside the rules directory) */
47 *filename, /**< It is the filename of the logfile(s) that match this rule (see this as a condition) */
48 *message, /**< Regexp to apply to message we get from syslog, the match them (see this as a condition) */
49 *type, /**< Type we will apply to the matched log message (see this as an affectation) */
50 *source_host, /**< Host we will apply to the matched log message (see this as an affectation) */
51 *source_path, /**< Log path we will apply to the matched log message (its like renaming the log, without mv it) (see this as an affectation) */
52 *tags; /**< tags we will apply to the matched log message (see this as an affectation) */
53 int todel; /**< If set to something other than 0, every matched rule will not be indexed */
54};
55
56/**
57 * @struct logfile
58 * @brief This structure allows us to attach a cursor position to a logfile,
59 * which is necessary to find new log entries
60 */
61struct logfile
62{
63 char *name; /**< Name of the log file */
64 fpos_t cursor; /**< Position of the cursor inside this logfile */
65 unsigned long long int
66 filesize; /**< File size, only help to see if a logfile is truncated, as far as i know */
67};
68
69/**
70 * @struct logmessage
71 * @brief This structure Contains needed information about a logfile that is going
72 * to be JSONed for ES.
73 */
74struct logmessage
75{
76 char *source_host, /**< Hostname */
77 *source_path, /**< Name of the logfile from where this message comes from */
78 timestamp[30], /**< Date of the log */
79 *type, /**< Type of message */
80 *message; /**< Log message to index in ES */
81 Eina_List *list_tags; /**< List of tags associated to this message */
82 int todel; /**< If set to something other than 0, this message wont be indexed */
83};
84
85int einadom_rules, /**< Used for eina_log inside rules.c */
86 einadom_spy, /**< Used for eina_log inside spy.c */
87 einadom_logfiles, /**< Used for eina_log inside logfiles.c */
88 einadom_send, /**< Used for eina_log inside send.c */
89 einadom_conf; /**< Used for eina_log inside conf.c */
90
91Eina_List *list_rules; /**< Used to store all the rules in memory, in an eina list */
92Eina_List *list_logfiles; /**< Used to store all the logfiles watched, in an eina list */
93
94Ecore_File_Monitor *efm; /**< Used for file monitoring by ecore */
95
96#endif
diff --git a/src/bin/libconf.c b/src/bin/libconf.c
new file mode 100644
index 0000000..2ce1e5c
--- /dev/null
+++ b/src/bin/libconf.c
@@ -0,0 +1,232 @@
1/*
2 * Copyright © 2011 ASP64 <guillaume.friloux@asp64.com>
3 *
4 * This program is free software: you can redistribute it and/or modify
5 * it under the terms of the GNU General Public License as published by
6 * the Free Software Foundation, either version 3 of the License, or
7 * (at your option) any later version.
8 *
9 * This program is distributed in the hope that it will be useful,
10 * but WITHOUT ANY WARRANTY; without even the implied warranty of
11 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 * GNU General Public License for more details.
13 *
14 * You should have received a copy of the GNU General Public License
15 * along with this program. If not, see <http://www.gnu.org/licenses/>.
16 *
17 */
18
19/**
20 * @file libconf.c
21 * @brief Allows reading of a configuration file
22 * @author Guillaume Friloux <guillaume.friloux@asp64.com>
23 * @version 1.0
24 *
25 * Allows reading of a configuration file.
26 * Every valid line of the configuration will be stored in an
27 * Eina list, and can be retrieved using callbacks
28 * @todo Being able to specify separation character between variable and value
29 *
30 */
31
32/**
33 * @page tutorial_libconf Libconf Documentation
34 * Libconf will allow you to parse basic configuration files of type :
35 *
36 * variable = value
37 *
38 *
39 * All you need to do is initialise the library, give fullpath to configuration
40 * file and read it.
41 *
42 * Example code :
43 * @code
44 * #include <libconf.h>
45 *
46 * int show_conf(char *variable, char *value)
47 * {
48 * printf("Variable=%s\tValue=%s\n", variable, value);
49 * return(0);
50 * }
51 *
52 * int main(int argc, char **argv)
53 * {
54 * if( argc < 2 ) return(1);
55 * struct libconfig myconf;
56 * eina_init();
57 * libconfig_init(argv[1], &myconf);
58 * libconfig_load(&myconf);
59 * libconfig_list(&myconf, show_conf);
60 * libconfig_free(&myconf);
61 * return(0);
62 * }
63 * @endcode
64 *
65 * @verbatim gcc -o main main.c `pkg-config --cflags libconf` `pkg-config --libs libconf` `pkg-config --cflags eina` @endverbatim
66 * @verbatim EINA_LOG_LEVEL=5 ./main /etc/docupack.conf@endverbatim
67 */
68#include "libconf.h"
69
70/**
71 * \fn int libconfig_init(char *file, struct libconfig *myconf)
72 * \brief Inits lib.
73 *
74 * \param file full path to configuration file
75 * \param myconf Pointer to a libconfig structure
76 * \return 0 if no error, 1 otherwise
77 */
78int libconfig_init(char *file, struct libconfig *myconf)
79{
80 strcpy(myconf->file, file);
81 myconf->lconfig = NULL;
82
83 ligconfig_einadom = eina_log_domain_register("Libconf", EINA_COLOR_ORANGE);
84
85 EINA_LOG_DOM_DBG(ligconfig_einadom, "Using configuration file %s", myconf->file);
86
87 return(0);
88}
89
90
91/**
92 * \fn int libconfig_load(struct libconfig *myconf)
93 * \brief Loads configuration file to store every variable into our Eina list
94 *
95 * \param myconf Pointer to a libconfig structure
96 * \return 0
97 */
98int libconfig_load(struct libconfig *myconf)
99{
100 FILE *fd;
101 char line[1024],
102 *ptr;
103 int nb;
104
105 EINA_LOG_DOM_DBG(ligconfig_einadom, "Loading configuration file");
106
107 fd = fopen(myconf->file, "r");
108 if( !fd )
109 {
110 EINA_LOG_DOM_ERR(ligconfig_einadom, "Can't open conf file \"%s\" : %s", myconf->file, strerror(errno));
111 return(-1);
112 }
113
114 while( 1 )
115 {
116 struct libconfig_entry *entrytmp;
117 int size;
118
119 nb = fscanf(fd, "%1024[^\n]\n", line);
120
121 // Did not got anything
122 if( nb != 1 )
123 break;
124
125 // Check if last char is '\r', if so we delete it
126 ptr = &line[strlen(line)-1];
127 if( ptr[0] == '\r' ) ptr[0] = 0;
128
129 // If this line is a comment, we go to next line
130 if( line[0] == '#' ) continue;
131
132 // We check that line has a '='
133 ptr = strchr(line, '=');
134 if( !ptr )
135 {
136 EINA_LOG_DOM_INFO(ligconfig_einadom, "Config entry is invalid : %s", line);
137 continue;
138 }
139
140 ptr[0] = 0;
141
142 ptr = &ptr[1];
143
144 // We delete undesired spaces
145 while( ( ptr[0] == 32 ) || ( ptr[0] == 9 ) )
146 ptr = &ptr[1];
147
148 size = strlen(ptr);
149 while( ( ptr[size-1] == 32 ) || ( ptr[size-1] == 9 ) )
150 {
151 ptr[size-1] = 0;
152 size = strlen(ptr);
153 }
154
155 size = strlen(line);
156 while( ( line[size-1] == 32 ) || ( line[size-1] == 9 ) )
157 {
158 line[size-1] = 0;
159 size = strlen(line);
160 }
161
162
163 entrytmp = malloc( sizeof(struct libconfig_entry) );
164
165 entrytmp->var = malloc( sizeof(char) * ( strlen(line) + 1 ) );
166 strcpy(entrytmp->var, line);
167
168 entrytmp->value = malloc( sizeof(char) * ( strlen(ptr) + 1 ) );
169 strcpy(entrytmp->value, ptr);
170
171 EINA_LOG_DOM_DBG(ligconfig_einadom, "Adding %s<->%s", entrytmp->var, entrytmp->value);
172 myconf->lconfig = eina_list_prepend(myconf->lconfig, entrytmp);
173 }
174
175 fclose(fd);
176
177 return(0);
178}
179
180/**
181 * \fn int libconfig_list(struct libconfig *myconf, int (*callback_function)(char *variable, char *value))
182 * \brief Will send to a callback every entry of the Eina list
183 *
184 * \param myconf Pointer to a libconfig structure
185 * \param callback_function Callback to call for each entry
186 * \return 0
187 */
188int libconfig_list(struct libconfig *myconf, int (*callback_function)(char *variable, char *value))
189{
190 Eina_List *l;
191 struct libconfig_entry *myentry;
192
193 EINA_LIST_FOREACH(myconf->lconfig, l, myentry)
194 callback_function(myentry->var, myentry->value);
195
196 return(0);
197}
198
199/**
200 * \fn int libconfig_free(struct libconfig *myconf)
201 * \brief Will free our eina list
202 *
203 * \param myconf Pointer to a libconfig structure
204 * \return 0
205 */
206int libconfig_free(struct libconfig *myconf)
207{
208 Eina_List *l;
209 struct libconfig_entry *myentry;
210
211 EINA_LIST_FOREACH(myconf->lconfig, l, myentry)
212 {
213 free(myentry->var);
214 free(myentry->value);
215 free(myentry);
216 }
217 eina_list_free(myconf->lconfig);
218 return(0);
219}
220
221/**
222 * @fn void libconfig_version(char *version)
223 * @brief Gets revision number of the library
224 *
225 * @param version buffer to use to store revision number
226 *
227 */
228void libconfig_version(char *version)
229{
230 strcpy(version, REVISION);
231 return;
232}
diff --git a/src/bin/libconf.h b/src/bin/libconf.h
new file mode 100644
index 0000000..a54a71e
--- /dev/null
+++ b/src/bin/libconf.h
@@ -0,0 +1,66 @@
1/*
2 * Copyright © 2011 ASP64 <guillaume.friloux@asp64.com>
3 *
4 * This program is free software: you can redistribute it and/or modify
5 * it under the terms of the GNU General Public License as published by
6 * the Free Software Foundation, either version 3 of the License, or
7 * (at your option) any later version.
8 *
9 * This program is distributed in the hope that it will be useful,
10 * but WITHOUT ANY WARRANTY; without even the implied warranty of
11 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 * GNU General Public License for more details.
13 *
14 * You should have received a copy of the GNU General Public License
15 * along with this program. If not, see <http://www.gnu.org/licenses/>.
16 *
17 */
18
19/**
20 * @file libconf.h
21 * @brief Contains structs and prototypes of libconf
22 * @author Guillaume Friloux <guillaume.friloux@asp64.com>
23 * @version 1.0
24 *
25 * Contains structs and prototypes of libconf
26 *
27 */
28
29#include <string.h>
30#include <sys/types.h>
31#include <sys/stat.h>
32#include <fcntl.h>
33#include <unistd.h>
34#include <errno.h>
35#include <Eina.h>
36
37#ifndef LIBCONFVARS
38#define LIBCONFVARS
39/**
40 * \struct libconfig
41 * \brief Main structure
42 */
43struct libconfig
44{
45 char file[512]; /**< Name of config file */
46 Eina_List *lconfig; /**< List of variables */
47};
48
49/**
50 * \struct libconfig_entry
51 * \brief Structure containing information about one config entry
52 */
53struct libconfig_entry
54{
55 char *var, /**< Variable name */
56 *value; /**< Value for this variable */
57};
58
59int ligconfig_einadom; /**< Eina DOM to use for eina logs */
60#endif
61
62int libconfig_init(char *file, struct libconfig *myconf);
63int libconfig_load(struct libconfig *myconf);
64int libconfig_list(struct libconfig *myconf, int (*callback_function)(char *variable, char *value));
65int libconfig_free(struct libconfig *myconf);
66void libconfig_version(char *version);
diff --git a/src/bin/log.txt b/src/bin/log.txt
new file mode 100644
index 0000000..45d27e1
--- /dev/null
+++ b/src/bin/log.txt
@@ -0,0 +1,181 @@
1==22091== Memcheck, a memory error detector
2==22091== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
3==22091== Using Valgrind-3.6.0 and LibVEX; rerun with -h for copyright info
4==22091== Command: ./smman
5==22091==
6DBG<22091>:eina_module eina_module.c:709 eina_module_list_load() array 0x46b29b0, count 0
7DBG<22091>:eina_mempool eina_mempool.c:155 eina_mempool_register() be=0x42f2640, name=0x42ee351
8DBG<22091>:eina_mempool eina_mempool.c:155 eina_mempool_register() be=0x42f2660, name=0x42f15a3
9DBG<22091>:eina_mempool eina_mempool.c:337 eina_mempool_add() name=chained_mempool, context=list, options=
10DBG<22091>:eina_mempool eina_mempool.c:344 eina_mempool_add() name=chained_mempool, context=list, options=, mp=0x46b3020
11DBG<22091>:eina_mempool eina_mempool.c:337 eina_mempool_add() name=chained_mempool, context=list_accounting, options=
12DBG<22091>:eina_mempool eina_mempool.c:344 eina_mempool_add() name=chained_mempool, context=list_accounting, options=, mp=0x46b30e8
13DBG<22091>:eina_mempool eina_mempool.c:337 eina_mempool_add() name=chained_mempool, context=matrixsparse_cell, options=
14DBG<22091>:eina_mempool eina_mempool.c:344 eina_mempool_add() name=chained_mempool, context=matrixsparse_cell, options=, mp=0x46b4018
15DBG<22091>:eina_mempool eina_mempool.c:337 eina_mempool_add() name=chained_mempool, context=matrixsparse_row, options=
16DBG<22091>:eina_mempool eina_mempool.c:344 eina_mempool_add() name=chained_mempool, context=matrixsparse_row, options=, mp=0x46b40e8
17DBG<22091>:eina_mempool eina_mempool.c:337 eina_mempool_add() name=chained_mempool, context=rectangle-alloc, options=
18DBG<22091>:eina_mempool eina_mempool.c:344 eina_mempool_add() name=chained_mempool, context=rectangle-alloc, options=, mp=0x46b4338
19DBG<22091>:eina_mempool eina_mempool.c:337 eina_mempool_add() name=chained_mempool, context=rectangle, options=
20DBG<22091>:eina_mempool eina_mempool.c:344 eina_mempool_add() name=chained_mempool, context=rectangle, options=, mp=0x46b4408
21DBG<22091>:eina_mempool eina_mempool.c:337 eina_mempool_add() name=chained_mempool, context=QuadTree Item, options=
22DBG<22091>:eina_mempool eina_mempool.c:344 eina_mempool_add() name=chained_mempool, context=QuadTree Item, options=, mp=0x46b4550
23DBG<22091>:eina_mempool eina_mempool.c:337 eina_mempool_add() name=chained_mempool, context=QuadTree Root, options=
24DBG<22091>:eina_mempool eina_mempool.c:344 eina_mempool_add() name=chained_mempool, context=QuadTree Root, options=, mp=0x46b4620
25INF<22091>:ecore ecore_main.c:548 _ecore_main_loop_init() enter
26INF<22091>:ecore ecore_main.c:585 _ecore_main_loop_init() leave
27DBG<22091>:ecore ecore_time.c:152 _ecore_time_init() using CLOCK_MONOTONIC.
28DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed626b0 (/usr/local/bin), slen=14
29DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed626bf (/usr/bin), slen=8
30DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed626c8 (/bin), slen=4
31DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed626cd (/usr/local/sbin), slen=15
32DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed626dd (/usr/sbin), slen=9
33DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed626e7 (/sbin), slen=5
34DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed626ed (/opt/java/jre/bin), slen=17
35DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed626ff (/usr/lib/perl5/vendor_perl/bin), slen=30
36DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed6271e (/usr/bin/core_perl), slen=18
37DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed62731 (/opt/qt/bin), slen=11
38DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed6273d (/usr/local/bin), slen=14
39DBG<22091>:eina_share eina_stringshare.c:658 eina_stringshare_add_length() str=0xbed6274c (/opt/e17/bin), slen=12
40INF<22091>:ecore ecore_main.c:193 _ecore_epoll_add() adding poll on 4 00000001
41DBG<22091>:Libconf libconf.c:85 libconfig_init() Using configuration file /etc/smman/smman.conf
42DBG<22091>:Libconf libconf.c:105 libconfig_load() Loading configuration file
43DBG<22091>:Libconf libconf.c:171 libconfig_load() Adding server<->http://localhost:9200/logstash/events/
44DBG<22091>:smman_conf conf.c:75 conf_load_var() Setting ES server to server
45DBG<22091>:smman_rules rules.c:55 rules_load() Found rule file tags_test
46DBG<22091>:Libconf libconf.c:85 libconfig_init() Using configuration file /etc/smman/rules.d/tags_test
47DBG<22091>:Libconf libconf.c:105 libconfig_load() Loading configuration file
48DBG<22091>:Libconf libconf.c:171 libconfig_load() Adding filename<->/var/log/slim.log
49DBG<22091>:Libconf libconf.c:171 libconfig_load() Adding tags<->test2,test3
50INF<22091>:smman_rules rules.c:191 rules_print()
51[tags_test]
52 filename = /var/log/slim.log
53 message = (null)
54 type = (null)
55 source_host = (null)
56 source_path = (null)
57 tags = test2,test3
58 delete = 0
59
60
61DBG<22091>:smman_spy spy.c:71 spy_addwatcher() Found 1 results for /var/log/slim.log
62INF<22091>:smman_logfiles logfiles.c:84 logfiles_print() Name = /var/log/slim.log Cursor = 100
63DBG<22091>:smman_spy spy.c:130 spy_event() Event on /var/log/slim.log ! 0x4735850 - 0x47358e0
64DBG<22091>:smman_spy spy.c:152 spy_event() Event on /var/log/slim.log - 100 !
65ERR<22091>:smman_spy spy.c:269 spy_extract_new_lines() ==22091== Use of uninitialised value of size 4
66==22091== at 0x43987B6: ??? (in /lib/libc-2.12.2.so)
67==22091== by 0x439BC48: vfprintf (in /lib/libc-2.12.2.so)
68==22091== by 0x439E3C1: ??? (in /lib/libc-2.12.2.so)
69==22091== by 0x4399312: vfprintf (in /lib/libc-2.12.2.so)
70==22091== by 0x42D561E: eina_log_print_cb_stderr (in /usr/lib/libeina.so.1.0.0)
71==22091== by 0x42D6CD3: eina_log_print (in /usr/lib/libeina.so.1.0.0)
72==22091== by 0x8049DA9: spy_extract_new_lines (spy.c:269)
73==22091== by 0x804A145: spy_event (spy.c:156)
74==22091== by 0x404F2CC: _ecore_file_monitor_inotify_handler (ecore_file_monitor_inotify.c:215)
75==22091== by 0x406E900: _ecore_main_loop_iterate_internal (ecore_main.c:1312)
76==22091== by 0x406EACE: ecore_main_loop_begin (ecore_main.c:663)
77==22091== by 0x80493A9: main (main.c:137)
78==22091==
79==22091== Conditional jump or move depends on uninitialised value(s)
80==22091== at 0x43987BE: ??? (in /lib/libc-2.12.2.so)
81==22091== by 0x439BC48: vfprintf (in /lib/libc-2.12.2.so)
82==22091== by 0x439E3C1: ??? (in /lib/libc-2.12.2.so)
83==22091== by 0x4399312: vfprintf (in /lib/libc-2.12.2.so)
84==22091== by 0x42D561E: eina_log_print_cb_stderr (in /usr/lib/libeina.so.1.0.0)
85==22091== by 0x42D6CD3: eina_log_print (in /usr/lib/libeina.so.1.0.0)
86==22091== by 0x8049DA9: spy_extract_new_lines (spy.c:269)
87==22091== by 0x804A145: spy_event (spy.c:156)
88==22091== by 0x404F2CC: _ecore_file_monitor_inotify_handler (ecore_file_monitor_inotify.c:215)
89==22091== by 0x406E900: _ecore_main_loop_iterate_internal (ecore_main.c:1312)
90==22091== by 0x406EACE: ecore_main_loop_begin (ecore_main.c:663)
91==22091== by 0x80493A9: main (main.c:137)
92==22091==
93==22091== Conditional jump or move depends on uninitialised value(s)
94==22091== at 0x439C1B0: vfprintf (in /lib/libc-2.12.2.so)
95==22091== by 0x439E3C1: ??? (in /lib/libc-2.12.2.so)
96==22091== by 0x4399312: vfprintf (in /lib/libc-2.12.2.so)
97==22091== by 0x42D561E: eina_log_print_cb_stderr (in /usr/lib/libeina.so.1.0.0)
98==22091== by 0x42D6CD3: eina_log_print (in /usr/lib/libeina.so.1.0.0)
99==22091== by 0x8049DA9: spy_extract_new_lines (spy.c:269)
100==22091== by 0x804A145: spy_event (spy.c:156)
101==22091== by 0x404F2CC: _ecore_file_monitor_inotify_handler (ecore_file_monitor_inotify.c:215)
102==22091== by 0x406E900: _ecore_main_loop_iterate_internal (ecore_main.c:1312)
103==22091== by 0x406EACE: ecore_main_loop_begin (ecore_main.c:663)
104==22091== by 0x80493A9: main (main.c:137)
105==22091==
106==22091== Conditional jump or move depends on uninitialised value(s)
107==22091== at 0x4399EAE: vfprintf (in /lib/libc-2.12.2.so)
108==22091== by 0x439E3C1: ??? (in /lib/libc-2.12.2.so)
109==22091== by 0x4399312: vfprintf (in /lib/libc-2.12.2.so)
110==22091== by 0x42D561E: eina_log_print_cb_stderr (in /usr/lib/libeina.so.1.0.0)
111==22091== by 0x42D6CD3: eina_log_print (in /usr/lib/libeina.so.1.0.0)
112==22091== by 0x8049DA9: spy_extract_new_lines (spy.c:269)
113==22091== by 0x804A145: spy_event (spy.c:156)
114==22091== by 0x404F2CC: _ecore_file_monitor_inotify_handler (ecore_file_monitor_inotify.c:215)
115==22091== by 0x406E900: _ecore_main_loop_iterate_internal (ecore_main.c:1312)
116==22091== by 0x406EACE: ecore_main_loop_begin (ecore_main.c:663)
117==22091== by 0x80493A9: main (main.c:137)
118==22091==
119FPOS 0 <-> 0
120DBG<22091>:smman_spy spy.c:293 spy_extract_new_lines() Empty line hack
121DBG<22091>:smman_send send.c:74 send_logmessage() JSON : { "@source" : "file://Jetdail/var/log/slim.log", "@type" : "syslog", "@tags" : [ "test2","test3" ], "@fields" : { }, "@message" : "** (gedit:6691): CRITICAL **: gedit_spell_checker_language_to_key: assertion `lang != NULL' failed", "@timestamp" : "2011-01-24T17:38:19.000000Z", "@source_host" : "Jetdail", "@source_path" : "/var/log/slim.log"}
122DBG<22091>:smman_spy spy.c:130 spy_event() Event on /var/log/slim.log ! 0x4735850 - 0x47358e0
123DBG<22091>:smman_spy spy.c:152 spy_event() Event on /var/log/slim.log - 200 !
124ERR<22091>:smman_spy spy.c:269 spy_extract_new_lines() FPOS 0 <-> 0
125DBG<22091>:smman_spy spy.c:293 spy_extract_new_lines() Empty line hack
126DBG<22091>:smman_send send.c:74 send_logmessage() JSON : { "@source" : "file://Jetdail/var/log/slim.log", "@type" : "syslog", "@tags" : [ "test2","test3" ], "@fields" : { }, "@message" : "** (gedit:6691): CRITICAL **: gedit_spell_checker_language_to_key: assertion `lang != NULL' failed", "@timestamp" : "2011-01-24T17:38:20.000000Z", "@source_host" : "Jetdail", "@source_path" : "/var/log/slim.log"}
127DBG<22091>:smman_spy spy.c:130 spy_event() Event on /var/log/slim.log ! 0x4735850 - 0x47358e0
128DBG<22091>:smman_spy spy.c:152 spy_event() Event on /var/log/slim.log - 300 !
129ERR<22091>:smman_spy spy.c:269 spy_extract_new_lines() FPOS 0 <-> 0
130DBG<22091>:smman_spy spy.c:293 spy_extract_new_lines() Empty line hack
131DBG<22091>:smman_send send.c:74 send_logmessage() JSON : { "@source" : "file://Jetdail/var/log/slim.log", "@type" : "syslog", "@tags" : [ "test2","test3" ], "@fields" : { }, "@message" : "** (gedit:6691): CRITICAL **: gedit_spell_checker_language_to_key: assertion `lang != NULL' failed", "@timestamp" : "2011-01-24T17:38:20.000000Z", "@source_host" : "Jetdail", "@source_path" : "/var/log/slim.log"}
132DBG<22091>:smman_spy spy.c:130 spy_event() Event on /var/log/slim.log ! 0x4735850 - 0x47358e0
133DBG<22091>:smman_spy spy.c:152 spy_event() Event on /var/log/slim.log - 400 !
134ERR<22091>:smman_spy spy.c:269 spy_extract_new_lines() FPOS 0 <-> 0
135DBG<22091>:smman_spy spy.c:293 spy_extract_new_lines() Empty line hack
136DBG<22091>:smman_send send.c:74 send_logmessage() JSON : { "@source" : "file://Jetdail/var/log/slim.log", "@type" : "syslog", "@tags" : [ "test2","test3" ], "@fields" : { }, "@message" : "** (gedit:6691): CRITICAL **: gedit_spell_checker_language_to_key: assertion `lang != NULL' failed", "@timestamp" : "2011-01-24T17:38:21.000000Z", "@source_host" : "Jetdail", "@source_path" : "/var/log/slim.log"}
137DBG<22091>:smman_spy spy.c:130 spy_event() Event on /var/log/slim.log ! 0x4735850 - 0x47358e0
138DBG<22091>:smman_spy spy.c:152 spy_event() Event on /var/log/slim.log - 500 !
139ERR<22091>:smman_spy spy.c:269 spy_extract_new_lines() FPOS 0 <-> 0
140DBG<22091>:smman_spy spy.c:293 spy_extract_new_lines() Empty line hack
141DBG<22091>:smman_send send.c:74 send_logmessage() JSON : { "@source" : "file://Jetdail/var/log/slim.log", "@type" : "syslog", "@tags" : [ "test2","test3" ], "@fields" : { }, "@message" : "** (gedit:6691): CRITICAL **: gedit_spell_checker_language_to_key: assertion `lang != NULL' failed", "@timestamp" : "2011-01-24T17:38:21.000000Z", "@source_host" : "Jetdail", "@source_path" : "/var/log/slim.log"}
142DBG<22091>:smman_spy spy.c:130 spy_event() Event on /var/log/slim.log ! 0x4735850 - 0x47358e0
143DBG<22091>:smman_spy spy.c:148 spy_event() WTF TRUNC
144DBG<22091>:smman_spy spy.c:152 spy_event() Event on /var/log/slim.log - 0 !
145ERR<22091>:smman_spy spy.c:269 spy_extract_new_lines() FPOS 0 <-> 74668116
146DBG<22091>:smman_send send.c:74 send_logmessage() JSON : { "@source" : "file://Jetdail/var/log/slim.log", "@type" : "syslog", "@tags" : [ "test2","test3" ], "@fields" : { }, "@message" : "", "@timestamp" : "2011-01-24T17:38:23.000000Z", "@source_host" : "Jetdail", "@source_path" : "/var/log/slim.log"}
147DBG<22091>:smman_spy spy.c:130 spy_event() Event on /var/log/slim.log ! 0x4735850 - 0x47358e0
148DBG<22091>:smman_spy spy.c:148 spy_event() WTF TRUNC
149DBG<22091>:smman_spy spy.c:152 spy_event() Event on /var/log/slim.log - 0 !
150ERR<22091>:smman_spy spy.c:269 spy_extract_new_lines() FPOS 0 <-> 74668116
151DBG<22091>:smman_send send.c:74 send_logmessage() JSON : { "@source" : "file://Jetdail/var/log/slim.log", "@type" : "syslog", "@tags" : [ "test2","test3" ], "@fields" : { }, "@message" : "", "@timestamp" : "2011-01-24T17:38:24.000000Z", "@source_host" : "Jetdail", "@source_path" : "/var/log/slim.log"}
152DBG<22091>:smman_spy spy.c:130 spy_event() Event on /var/log/slim.log ! 0x4735850 - 0x47358e0
153DBG<22091>:smman_spy spy.c:152 spy_event() Event on /var/log/slim.log - 0 !
154ERR<22091>:smman_spy spy.c:269 spy_extract_new_lines() FPOS 0 <-> 0
155DBG<22091>:smman_spy spy.c:293 spy_extract_new_lines() Empty line hack
156DBG<22091>:smman_send send.c:74 send_logmessage() JSON : { "@source" : "file://Jetdail/var/log/slim.log", "@type" : "syslog", "@tags" : [ "test2","test3" ], "@fields" : { }, "@message" : "** (gedit:6691): CRITICAL **: gedit_spell_checker_language_to_key: assertion `lang != NULL' failed", "@timestamp" : "2011-01-24T17:38:25.000000Z", "@source_host" : "Jetdail", "@source_path" : "/var/log/slim.log"}
157DBG<22091>:smman_spy spy.c:130 spy_event() Event on /var/log/slim.log ! 0x4735850 - 0x47358e0
158DBG<22091>:smman_spy spy.c:152 spy_event() Event on /var/log/slim.log - 100 !
159ERR<22091>:smman_spy spy.c:269 spy_extract_new_lines() FPOS 0 <-> 0
160DBG<22091>:smman_send send.c:74 send_logmessage() JSON : { "@source" : "file://Jetdail/var/log/slim.log", "@type" : "syslog", "@tags" : [ "test2","test3" ], "@fields" : { }, "@message" : "error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 13118263", "@timestamp" : "2011-01-24T17:38:33.000000Z", "@source_host" : "Jetdail", "@source_path" : "/var/log/slim.log"}
161DBG<22091>:smman_spy spy.c:130 spy_event() Event on /var/log/slim.log ! 0x4735850 - 0x47358e0
162DBG<22091>:smman_spy spy.c:152 spy_event() Event on /var/log/slim.log - 678 !
163ERR<22091>:smman_spy spy.c:269 spy_extract_new_lines() FPOS 0 <-> 0
164DBG<22091>:smman_send send.c:74 send_logmessage() JSON : { "@source" : "file://Jetdail/var/log/slim.log", "@type" : "syslog", "@tags" : [ "test2","test3" ], "@fields" : { }, "@message" : "error 4: BadPixmap (invalid Pixmap parameter) request 54 minor 0 serial 13121431", "@timestamp" : "2011-01-24T17:38:33.000000Z", "@source_host" : "Jetdail", "@source_path" : "/var/log/slim.log"}
165==22091==
166==22091== HEAP SUMMARY:
167==22091== in use at exit: 80,900 bytes in 3,962 blocks
168==22091== total heap usage: 7,140 allocs, 3,178 frees, 622,324 bytes allocated
169==22091==
170==22091== LEAK SUMMARY:
171==22091== definitely lost: 0 bytes in 0 blocks
172==22091== indirectly lost: 0 bytes in 0 blocks
173==22091== possibly lost: 0 bytes in 0 blocks
174==22091== still reachable: 80,900 bytes in 3,962 blocks
175==22091== suppressed: 0 bytes in 0 blocks
176==22091== Reachable blocks (those to which a pointer was found) are not shown.
177==22091== To see them, rerun with: --leak-check=full --show-reachable=yes
178==22091==
179==22091== For counts of detected and suppressed errors, rerun with: -v
180==22091== Use --track-origins=yes to see where uninitialised values come from
181==22091== ERROR SUMMARY: 68 errors from 4 contexts (suppressed: 51 from 10)
diff --git a/src/bin/logfiles.c b/src/bin/logfiles.c
new file mode 100644
index 0000000..9865a7c
--- /dev/null
+++ b/src/bin/logfiles.c
@@ -0,0 +1,209 @@
1/*
2 * Copyright © 2011 ASP64 <guillaume.friloux@asp64.com>
3 *
4 * This program is free software: you can redistribute it and/or modify
5 * it under the terms of the GNU General Public License as published by
6 * the Free Software Foundation, either version 3 of the License, or
7 * (at your option) any later version.
8 *
9 * This program is distributed in the hope that it will be useful,
10 * but WITHOUT ANY WARRANTY; without even the implied warranty of
11 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 * GNU General Public License for more details.
13 *
14 * You should have received a copy of the GNU General Public License
15 * along with this program. If not, see <http://www.gnu.org/licenses/>.
16 *
17 */
18
19/**
20 * @file logfiles.c
21 * @brief Manages log files list
22 * @author Guillaume Friloux <guillaume.friloux@asp64.com>
23 * @version 1.0
24 *
25 * Manages log files list
26 * @see logfile
27 * @see list_logfiles
28 */
29#include "logfiles.h"
30
31/**
32 * @fn int logfiles_exist(char *logfile)
33 * @brief Checks in the list of log files we are watching if we
34 * already watch a given logfile
35 *
36 * @param logfile (char *) Name of the logfile to check
37 *
38 * @return 0 if not found, 1 if found
39 */
40int logfiles_exist(char *logfile)
41{
42 Eina_List *l;
43 struct logfile *foundlogfile = NULL;
44
45 EINA_LIST_FOREACH(list_logfiles, l, foundlogfile)
46 {
47 if( !strcmp(foundlogfile->name, logfile) )
48 {
49 return(1);
50 }
51 }
52
53 return(0);
54}
55
56/**
57 * @fn int logfiles_add(struct logfile *new_logfile)
58 * @brief Adds a logfile struct inside the logfiles list
59 *
60 * @param new_logfile (struct logfile *) structure to add
61 *
62 * @return 0 if not found, 1 if found
63 */
64int logfiles_add(struct logfile *new_logfile)
65{
66 list_logfiles = eina_list_append(list_logfiles, new_logfile);
67 return(0);
68}
69
70/**
71 * @fn int logfiles_print(void)
72 * @brief Prints on stdout the list of logfiles. Only usefull for a bit of
73 * monitoring of what is going on
74 *
75 * @return 0 if not found, 1 if found
76 */
77int logfiles_print(void)
78{
79 Eina_List *l;
80 struct logfile *foundlogfile = NULL;
81
82 EINA_LIST_FOREACH(list_logfiles, l, foundlogfile)
83 {
84 EINA_LOG_DOM_INFO(einadom_logfiles, "Name = %s\tCursor = %d", foundlogfile->name, foundlogfile->cursor);
85 }
86 return(0);
87}
88
89/**
90 * @fn int logfiles_new(struct logfile **new_logfile, char *filename, fpos_t cursor, unsigned long long int filesize)
91 * @brief Will alloc a new logfile structure and set given values
92 *
93 * @param new_logfile (struct logfile *) structure to alloc
94 * @param filename (char *) Name of the logfile
95 * @param cursor (fpos_t) Position of the cursor
96 * @param filesize (unsigned long long int) Size of the file
97 *
98 * @return 0
99 */
100int logfiles_new(struct logfile **new_logfile, char *filename, fpos_t cursor, unsigned long long int filesize)
101{
102 *new_logfile = malloc(sizeof(struct logfile));
103 (*new_logfile)->name = malloc(sizeof(char) * ( strlen(filename) + 1 ) );
104 strcpy( (*new_logfile)->name, filename);
105 (*new_logfile)->cursor = cursor;
106 (*new_logfile)->filesize = filesize;
107
108 return(0);
109}
110
111/**
112 * @fn int logfiles_del(struct logfile **old_logfile)
113 * @brief This function will free an allocated logfile structure
114 *
115 * @param old_logfile (struct logfile **) structure to free
116 *
117 * @return 0
118 */
119int logfiles_del(struct logfile **old_logfile)
120{
121 if( !(*old_logfile) )
122 return(0);
123
124 if( (*old_logfile)->name )
125 free((*old_logfile)->name);
126
127 free((*old_logfile));
128 return(0);
129}
130
131/**
132 * @fn int logfiles_getend(char *logfile, fpos_t *pos_end)
133 * @brief This function will get a cursor to the end of the file
134 *
135 * @param logfile (char *) logfile involved
136 * @param pos_end (fpos_t *) pointer used to store the position
137 *
138 * @return 0 or -1 if an error occur
139 */
140int logfiles_getend(char *logfile, fpos_t *pos_end)
141{
142 FILE *fp;
143
144 // We get our cursor pos
145 fp = fopen(logfile, "r");
146 if( !fp )
147 {
148 EINA_LOG_DOM_ERR(einadom_logfiles, "Can't open %s : %s", logfile, strerror(errno));
149 return(-1);
150 }
151 fseek(fp, 0L, SEEK_END);
152 fgetpos(fp, pos_end);
153
154 fclose(fp);
155 return(0);
156}
157