Download Latest Version syslogd2-1.0.0.tz2 (757.2 kB)
Email in envelope

Get an email when there's a new version of Syslogd2

Home
Name Modified Size InfoDownloads / Week
docs 2023-01-26
README.txt 2024-12-04 4.0 kB
syslogd2-1.0.0.tz2 2024-12-04 757.2 kB
Totals: 3 Items   761.2 kB 0
-------------------------------------------------------
To get Syslogd2:
   Download a Syslogd2 tar-file file here. Untar with "tar -xjvf <basename.tz2>". (These updates tend to be infrequent)
        -- OR --
   Get the latest copy of Syslogd2 from the SVN repository: 
   1. Select the 'SVN' tab on this site.
   2. From the menu ('branches', 'tags', 'trunk') select 'trunk'.
   	This will take you to the latest code update I have posted.
      -- The 'Commit' column for each file contains the comment that was posted with that file the last time it was updated.
   3. On the dark grey bar below the site's menu-bar, select "Download Snapshot".
      This will download a zip-file to your local machine that (when unzipped) will contain the source code for Syslogd2.
		The zip file will create a new sub-directory structure into which all files will be placed.

   Note: I have recently been updating this svn repository only after I have run the 'new' code on my own box for a while and have some confidence it is stable.
   	In each update, I try to indicate my feel for the level of stability with notifications of any and all non-working features or features where I have noticed anomalous operation.
   	In each update, I indicate what 'fixes' I have applied to previous versions -- even if just removing debug statements or comments.
   	In each update, I also indicate what new features I have added to the system.
		The latest version of code in the svn repository is always my most stable version with all known issues resolved or highlighted.

      I also try (but do not always succeed) to keep the documentation site up-to-date with my feature additions.
      Thus the documentation site may describe features that are only avaialable (or only working) in the latest svn download and that may not yet exist in the more static 'files' download.

-------------------------------------------------------
To compile this project, download and un-tar/un-zip the source. Then:

   cd syslogd2*

   autoconf
   ./configure [--with-syslog_extras=<n>]
   make

The commands above will create several Syslogd2 'variants' and a set of testing tools in the '<build>/tools' sub-directory.
Each 'variant' is defined a different selection of compiler-symbols that enable/disable different features (see the disscussion at <https://syslogd2.sourceforge.io/misctopics.php#compileinstall> for details on how to create your own customized set of variants.

Syslogd2 may be started (as root) from the command-line with:  ./syslogd2<suffix> -c <config-file> [--systemd] [--ApplicationMode] ...
   Almost all command-line options may be moved into the configuration-file for easier management. The Syslogd2 documentation site (<https://syslogd2.sourcege.io>) describes how to do this.

Syslogd2 may also be installed as the primary syslog server for a Linux host (regardless of whether that host uses systemd or sysv init scripts).

Syslogd2 must always be started as the root user in order to access privileged sockets, privileged filesystem locations and to issue privileged system-calls (to change file ownership for instance).

-------------------------------------------------------
Documentation:
   Documentation for syslog can be found at <https://syslogd2.sourceforge.io> or by selecting the 'On-Line Project Documentation' tab on this site.
   Please use this documentation website (at <https://syslogd2.sourceforge.io>) as the most recent / most complete documentation for Syslogd2.

   Please post questions or comments with any errors or points of confusion / clarification to the wiki or email me directly at <mailto:ed@freesmeyer.com>

-------------------------------------------------------

Status of the Syslogd2 code-base:
-------------------------------------------------------
Ready for production testing and use.

All unit-level testing has been successful. All described features are implemented and have been thoroughly tested except where explicitly indicated in the documentation comments.
Source: README.txt, updated 2024-12-04