/usr/share/doc/prelude-manager/README is in prelude-manager 1.0.1-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 | Prelude-Manager is brought to you by PreludeIDS Technologies (http://www.prelude-ids.com),
Prelude-Manager Overview
========================
Prelude-Manager server is the Prelude events collector.
Prelude-Manager is a high availability server that accepts secured connections from
distributed sensors or other managers and saves received events to a media specified
by the user (database, logfile, mail, etc).
The server is a high availability server capable of handling large number of connections,
and processing large amounts of events. It uses a per client scheduling queues in order to
process events by severity fairly accross clients.
REQUIREMENTS
============
You need to install libprelude on your system before compiling Prelude-Manager.
IRC
===
If there's something you just can't find out elsewhere, you want to
give feedback directly to the authors or you're just bored, visit
#prelude on irc.freenode.net
Get Support
===========
Prelude-user mailing list archives can be accessed at:
http://lists.prelude-ids.org
Commercial Support is available through the PreludeIDS Technologies company:
http://www.prelude-ids.com, info@prelude-ids.com
Help development
================
1. SUBMITTING PATCHES
The Prelude source is constantly changing. If you want to submit a patch,
please do so from the most recent CVS source tree, subscribe to the
prelude-devel mailing list by sending a mail to:
prelude-devel-subscribe@prelude-ids.org
and post your patch with a description of functionality.
You can also attach patches to bugs on
http://trac.prelude-ids.org
2. BUGS
If you find any bugs, please report them to:
http://trac.prelude-ids.org
Please make sure that what you're reporting is actually a BUG and not
a problem on your side.
3. SUGGESTIONS
Subscribe to prelude-devel and give us your suggestions.
|