From a34ed607d8aa1a537e031ef342674c32bf0d6e88 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards This page reflects the status as of 2007-12-07. This page reflects the status as of 2007-12-19. development: 1.20.0 -
+ development: 1.21.0 -
change log -
download stable: 1.0.5 - change log -
--
cgit
From 6a4ab6d26e3a5b9e90c1b1e1a6bca42c79a6f06e Mon Sep 17 00:00:00 2001
From: Rainer Gerhards rsyslog status page
-Current Releases
-
stable: 1.0.5 - change log - download
-- cgit From e658ff8c43db22daee54dd70f2796cbded268353 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards$IncludeConfig /etc/some-included-file.conf
Directories can also be included. To do so, the name must end on a slash:
$IncludeConfig /etc/rsyslog.d/
And finally, only specific files matching a wildcard my be included
+from a directory:
$IncludeConfig /etc/rsyslog.d/*.conf
[rsyslog.conf overview] [manual index] [rsyslog site]
-- cgit From f4c2ccaf4ad673c5150b9d0fa9cae1ae0a69f85e Mon Sep 17 00:00:00 2001 From: Rainer GerhardsPlease note that in this description, only "*.conf" files would be read. The actual implementation, however, reads all files except for those starting with a dot. If you find this is a real big problem, please complain.
Sample:
$IncludeConfig /etc/some-included-file.conf
Directories can also be included. To do so, the name must end on a slash:
$IncludeConfig /etc/rsyslog.d/
And finally, only specific files matching a wildcard my be included
-from a directory:
And finally, only specific files matching a wildcard my be included +from a directory:
$IncludeConfig /etc/rsyslog.d/*.conf
[rsyslog.conf overview] [manual
--
cgit
From 9bf43f592d7e367db09d10e0d0e17060412f2400 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards This page reflects the status as of 2007-12-19. This page reflects the status as of 2007-12-23. development: 1.21.0 -
-change log -
-download development: 1.21.1 -
+change log -
+download stable: 1.0.5 - change log -
download This page reflects the status as of 2007-12-23. This page reflects the status as of 2007-12-28. development: 1.21.1 -
-change log -
-download development: 1.21.2 -
+change log -
+download stable: 1.0.5 - change log -
download December 2008 showed the appearance of a postgres
+really understood. December 2007 showed the appearance of a postgres
output module, contributed by sur5r. With 1.20.0, December is also the first
-time since the bughunt that we introduce other new features. It has been deciced
+time since the bug hunt that we introduce other new features. It has been decided
that we carefully will add features in order to not affect the overall project
-by these rare bugs. Still, the bughunt is top priortiy, but we need to have more
-data to analyse. Be sure to visit Rainer's syslog blog
+by these rare bugs. Still, the bug hunt is top priority, but we need to have more
+data to analyze. At then end of December, it looked like the bug was found (a
+race condition), but further confirmation from the field is required before
+declaring victory. December also brings the initial development on rsyslog v3,
+resulting in loadable input modules, now running on a separate thread each. On
+January, 2nd 2008, rsyslog 1.21.2 is re-released as rsyslog v2.0.0
+stable. This is a major milestone as far as the stable build is concerned. v3 is
+not yet officially announced. Other than the stable v2 build, v3 will not be
+backwards compatibile (including missing compatibility to stock sysklogd) for
+quite a while. Config file changes are required and some command line options do
+no longer work due to the new design. Be sure to visit Rainer's syslog blog
to get some more insight into the development and futures of rsyslog and syslog in general.
Don't be shy to post to either the blog or the
rsyslog forums. Rsyslog is an enhanced syslogd
-supporting, among others, MySQL,
PostgreSQL,
failover log
destinations, syslog/tcp,
-fine grain output format control, and the ability to filter on any message part.
-It is quite compatible to stock
-sysklogd and can be used as a drop-in replacement. Its
-advanced features make it suitable for enterprise-class,
-encryption protected syslog
-relay chains while at the same time being very easy to setup
-for the novice user. Visit the rsyslog status page to obtain current
-version information and ports. If you like rsyslog, you might want to lend us
-a helping hand. It doesn't require a lot of time - even a single mouse click
-helps. Learn how to help the rsyslog project. Follow the links below for the We have some in-depth papers on Also, there is an article from Dennis Olvany on
-Syslog-to-SQL with rsyslog-0.8.4 on FreeBSD 5.4
-(which unfortunately is a bit outdated now). Our rsyslog history page is for you if you would like to learn a little more
-on why there is an rsyslog at all. If you are interested why you should care
about rsyslog at all, you may want to read Rainer's essay on "why
the world needs another syslogd". Documentation is added continuously. Please note that the documentation here
-matches only the current version of rsyslog. If you use an older version, be sure
-to use the doc that came with it. You can also browse the following online resources: And don't forget about the rsyslog mailing list.
-If you are interested in the "backstage", you may find
-Rainer's
-blog an interesting read (filter on
syslog and rsyslog tags). Rsyslog is an enhanced syslogd
+
+supporting, among others, MySQL,
+PostgreSQL,
+failover log
+destinations, syslog/tcp,
+
+fine grain output format control, and the ability to filter on any message part.
+
+It is quite compatible to stock
+
+sysklogd and can be used as a drop-in replacement. Its
+
+advanced features make it suitable for enterprise-class,
+
+encryption protected syslog
+
+relay chains while at the same time being very easy to setup
+
+for the novice user. Visit the rsyslog status page to obtain current
+
+version information and ports. If you like rsyslog, you might want to lend us
+
+a helping hand. It doesn't require a lot of time - even a single mouse click
+
+helps. Learn how to help the rsyslog project. Follow the links below for the We have some in-depth papers on Also, there is an article from Dennis Olvany on
+
+Syslog-to-SQL with rsyslog-0.8.4 on FreeBSD 5.4
+
+(which unfortunately is a bit outdated now). Our rsyslog history page is for you if you would like to learn a little more
+
+on why there is an rsyslog at all. If you are interested why you should care
+about rsyslog at all, you may want to read Rainer's essay on "why
+the world needs another syslogd". Documentation is added continuously. Please note that the documentation here
+
+matches only the current version of rsyslog. If you use an older version, be sure
+
+to use the doc that came with it. You can also browse the following online resources: And don't forget about the rsyslog mailing list.
+
+If you are interested in the "backstage", you may find
+
+Rainer's
+
+blog an interesting read (filter on
+syslog and rsyslog tags). Type: global configuration directive Default: host Provided by: omgssapi Description: Specifies the service name used by the client when forwarding GSS-API wrapped messages. The GSS-API service names are constructed by appending '@' and a hostname following "@@" in each selector. Type: global configuration directive Default: none Default: encryption Provided by: omgssapi Description: Specifies GSS-API mode to use, which can be "none" - GSS-API
- is disabled, "integrity" - clients are authenticated and
- messages are checked for integrity, "encryption" - same as
- "integrity", but messages are also encrypted if both sides support it.
- Sample: Specifies GSS-API mode to use, which can be "integrity" - clients are authenticated and
+ messages are checked for integrity, "encryption" - same as
+ "integrity", but messages are also encrypted if both sides support it. Sample: [rsyslog.conf overview] [manual
diff --git a/doc/status.html b/doc/status.html
index 8a4f1556..86d1844c 100644
--- a/doc/status.html
+++ b/doc/status.html
@@ -4,17 +4,14 @@
This page reflects the status as of 2007-12-28. This page reflects the status as of 2008-01-01. development: 1.21.2 -
change log -
download stable: 1.0.5 - change log -
-download stable: 2.0.0 - change log -
+download Do NOT use versions prior to 1.10.1 or 1.0.1,
-because they contain a SQL injection vulnerability (read
-security advisory). Thankfully, a number of folks have begin to build packages and help port
rsyslog to other platforms. As such,
--
cgit
From 96e2f60ec61e1614709dd09a73a94701aca55161 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards This page reflects the status as of 2008-01-01. This page reflects the status as of 2008-01-24. development: 1.21.2 -
-change log -
-download stable: 2.0.0 - change log -
-download development: 3.10.2 -
+change log -
+download Be sure to read the
+rsyslog v3 compatibility document! stable: 2.0.1 - change log -
+download Thankfully, a number of folks have begin to build packages and help port
--
cgit
From 2dd6d08b5d4ec053095d532dc1540f6630553c9b Mon Sep 17 00:00:00 2001
From: Rainer Gerhards Type: global configuration directive Default: off Description: This directive allows to specify if actions should always be executed ("off," the default) or only if the previous action is suspended ("on"). This directive works hand-in-hand with the multiple actions per selector feature. It can be used, for example, to create rules that automatically switch destination servers or databases to a (set of) backup(s), if the primary server fails. Note that this feature depends on proper implementation of the suspend feature in the output module. All built-in output modules properly support it (most importantly the database write and the syslog message forwarder). This selector processes all messages it receives (*.*). It tries to forward every message to primary-syslog.example.com (via tcp). If it can not reach that server, it tries secondary-1-syslog.example.com, if that fails too, it tries secondary-2-syslog.example.com. If neither of these servers can be connected, the data is stored in /var/log/localbuffer. Please note that the secondaries and the local log buffer are only used if the one before them does not work. So ideally, /var/log/localbuffer will never receive a message. If one of the servers resumes operation, it automatically takes over processing again. We strongly advise not to use repeated line reduction together with ActionExecOnlyIfPreviousIsSuspended. It may lead to "interesting" and undesired results (but you can try it if you like). Sample: [rsyslog.conf overview] [manual
-index] [rsyslog site] This documentation is part of the
-rsyslog project. Type: global configuration directive Default: off Description: This directive allows to specify if actions should always be executed ("off," the default) or only if the previous action is suspended ("on"). This directive works hand-in-hand with the multiple actions per selector feature. It can be used, for example, to create rules that automatically switch destination servers or databases to a (set of) backup(s), if the primary server fails. Note that this feature depends on proper implementation of the suspend feature in the output module. All built-in output modules properly support it (most importantly the database write and the syslog message forwarder). This selector processes all messages it receives (*.*). It tries to forward every message to primary-syslog.example.com (via tcp). If it can not reach that server, it tries secondary-1-syslog.example.com, if that fails too, it tries secondary-2-syslog.example.com. If neither of these servers can be connected, the data is stored in /var/log/localbuffer. Please note that the secondaries and the local log buffer are only used if the one before them does not work. So ideally, /var/log/localbuffer will never receive a message. If one of the servers resumes operation, it automatically takes over processing again. We strongly advise not to use repeated line reduction together with ActionExecOnlyIfPreviousIsSuspended. It may lead to "interesting" and undesired results (but you can try it if you like). Sample: [rsyslog.conf overview] [manual
+index] [rsyslog site] This documentation is part of the
+rsyslog project. Type: global configuration directive Default: off Description: Also, there is an article from Dennis Olvany on
-
-Syslog-to-SQL with rsyslog-0.8.4 on FreeBSD 5.4
-
-(which unfortunately is a bit outdated now). Our rsyslog history page is for you if you would like to learn a little more
on why there is an rsyslog at all. If you are interested why you should care
diff --git a/modutils.patch b/modutils.patch
deleted file mode 100644
index 4dff7f35..00000000
--- a/modutils.patch
+++ /dev/null
@@ -1,65 +0,0 @@
-diff -u --new-file --recursive base/modules-2.0.0/depmod/modprobe.c ./modules-2.0.0/depmod/modprobe.c
---- base/modules-2.0.0/depmod/modprobe.c Mon Jun 10 05:29:08 1996
-+++ ./modules-2.0.0/depmod/modprobe.c Thu Aug 29 09:58:01 1996
-@@ -233,6 +233,13 @@
- verbose ("\r\t%s\n\t\t",cmd);
- int ret = system(cmd);
- #endif
-+ if ( fork() == 0 )
-+ {
-+ /* Child process. */
-+ if ( execlp("klogd", "klogd", "-i", (char *) 0) < 0 )
-+ fprintf(stderr, "Failure in signaling klogd.\n");
-+ exit(0);
-+ }
- return ret;
- }
- /*
-diff -u --new-file --recursive base/modules-2.0.0/insmod/insmod.c ./modules-2.0.0/insmod/insmod.c
---- base/modules-2.0.0/insmod/insmod.c Mon Jun 10 06:42:25 1996
-+++ ./modules-2.0.0/insmod/insmod.c Thu Aug 29 09:56:53 1996
-@@ -253,6 +253,18 @@
- ++n_stringpatches;
- }
-
-+
-+void signal_klogd() {
-+ if ( fork() == 0 )
-+ {
-+ if ( execlp("klogd", "klogd", "-i", (char *) 0) < 0 )
-+ fprintf(stderr, "Failure in signaling klogd.\n");
-+ exit(0);
-+ }
-+ return;
-+}
-+
-+
- int main(int argc, char **argv)
- {
- FILE *fp;
-@@ -983,6 +995,8 @@
- symvalue(sp) + addr, symtype, symname(sp));
- }
-
-+ signal_klogd();
-+
- if (nksyms > 0)
- free(ksymtab); /* it has done its job */
-
-@@ -1292,6 +1306,7 @@
- --argc;
- ++argv;
- }
-+ signal_klogd();
- return errors;
- }
- /* else recursive removal */
-@@ -1353,6 +1368,8 @@
- break;
- }
- }
-+
-+ signal_klogd();
-
- return errors;
- }
diff --git a/syslog.conf b/syslog.conf
deleted file mode 100644
index 801f35fb..00000000
--- a/syslog.conf
+++ /dev/null
@@ -1,46 +0,0 @@
-# /etc/syslog.conf - Configuration file for syslogd(8)
-#
-# For info about the format of this file, see "man syslog.conf".
-#
-*.=debug -/usr/adm/debug
-*.warning /usr/adm/syslog
-
-# Store critical stuff in critical
-#
-*.=crit;kern.none /var/adm/critical
-
-# Kernel messages are first, stored in the kernel file,
-# critical messages and higher ones also go to another
-# host and to the console
-#
-kern.* /var/adm/kernel
-kern.crit @finlandia
-kern.crit /dev/console
-kern.info;kern.!err /var/adm/kernel-info
-
-# The tcp wrapper loggs with mail.info, we display all
-# the connections on tty12
-#
-mail.=info /dev/tty12
-
-# Store all mail concearning stuff in a file
-#
-mail.*;mail.!=info -/var/adm/mail
-
-# Log all mail.info and news.info messages to info
-#
-mail,news.=info -/var/adm/info
-
-# Log info and notice mesages to messages file
-#
-*.=info;*.=notice;mail.none -/usr/adm/messages
-#*.=info;mail,news.none -/usr/adm/messages
-
-# Emergency messages will be displayed using wall
-#
-*.=emerg *
-
-# Messages of the priority alert will be directed
-# to the operator
-#
-*.alert root,joey
diff --git a/syslog_tst.c b/syslog_tst.c
deleted file mode 100644
index 40896b31..00000000
--- a/syslog_tst.c
+++ /dev/null
@@ -1,76 +0,0 @@
-/* Program to test daemon logging. */
-
-/*
- * Sat Dec 11 12:07:50 CST 1993: Dr. Wettstein
- * Compiles clean with -Wall. Renamed for first public distribution.
- * Use this freely but if you make a ton of money with it I
- * expect a cut... :-)
- *
- * Thu Jan 6 11:52:10 CST 1994: Dr. Wettstein
- * Added support for reading getting log input from the standard
- * input. To activate this use a - as the single arguement to the
- * the program. Note that there is a hack in the code to pause
- * after each 1K has been written. This eliminates what appears
- * to be a problem with overrunning a UNIX domain socket with
- * excessive amounts of input.
- */
-#include "config.h"
-
-
-#include This page reflects the status as of 2008-01-24. This page reflects the status as of 2008-02-12. development: 3.10.2 -
-change log -
-download development: 3.11.0 -
+change log -
+download Be sure to read the
rsyslog v3 compatibility document! stable: 2.0.1 - change log -
-download stable: 2.0.2 - change log -
+download Thankfully, a number of folks have begin to build packages and help port
--
cgit
From e14dbae80c2f0541a67f23e00c44b7bd43f85bf1 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards rsyslog status page
-Current Releases
-rsyslog status page
-Current Releases
-RSyslog - Documentation
-
-
-
-
-
-
-RSyslog - Documentation
+
+
+
+
+
+
+
+
+
+
+
+
+
+$GssForwardServiceName
$GssMode
$GssMode Encryptionrsyslog status page
-Current Releases
Platforms
rsyslog status page
-Current Releases
-
+Documentation for 3.x is currently sparse. If you need assistance, please
+post in the rsyslog forums!Platforms
$ActionExecOnlyIfPreviousIsSuspended
-*.* @@primary-syslog.example.com
-
$ActionExecOnlyIfPreviousIsSuspended on
-
& @@secondary-1-syslog.example.com # & is used to have more than one action for
-
& @@secondary-2-syslog.example.com # the same selector - the mult-action feature
-
& /var/log/localbuffer
-
$ActionExecOnlyIfPreviousIsSuspended off # to re-set it for the next selector
-Copyright © 2007 by Rainer Gerhards and
-Adiscon. Released under the GNU GPL
-version 2 or higher.$ActionExecOnlyIfPreviousIsSuspended
+*.* @@primary-syslog.example.com
+
$ActionExecOnlyIfPreviousIsSuspended on
+
& @@secondary-1-syslog.example.com # & is used to have more than one action for
+
& @@secondary-2-syslog.example.com # the same selector - the mult-action feature
+
& /var/log/localbuffer
+
$ActionExecOnlyIfPreviousIsSuspended off # to re-set it for the next selector
+Copyright © 2007 by Rainer Gerhards and
+Adiscon. Released under the GNU GPL
+version 2 or higher.
-
-->$ActionExecOnlyIfPreviousIsSuspended
+$ActionExecOnlyWhenPreviousIsSuspended
rsyslog status page
-Current Releases
-
Documentation for 3.x is currently sparse. If you need assistance, please
post in the rsyslog forums!Platforms
Documentation for 3.x is currently sparse. If you need assistance, please
post in the rsyslog forums!
stable: 2.0.2 - change log - -download
+downloadThankfully, a number of folks have begin to build packages and help port
--
cgit
From dd70fc145fc8b8d94bfa98fc25e4ccd5a073859a Mon Sep 17 00:00:00 2001
From: Rainer Gerhards
Sample:
$EscapeControlCharactersOnReceive on
This page lists the known bugs rsyslog has to offer. Please note that -we also have a - -bug tracker at sourceforge.net. This list here contains more architectural -things while the bug tracker most often lists things that you will actually -experience. Please be sure to visit the bug tracker in addition to this list -here.
-This list has last been updated on 2007-07-30 by +
This page lists the known bugs rsyslog has to offer. It lists +old and esoteric bugs. A live list of bugs is contained in our bugzilla. +Please visit +http://www.rsyslog.com/bugs to see what we +have. There, you can also open your own bug report if you think you found one.
+This list has last been updated on 2008-02-12 by Rainer Gerhards.
We have some reports that rsyslogd, if compiled with multi-threading enabled, -segfaults in some environments. We are actively looking at fixing this issue, -but as it does not occur in our lab environment, that unfortunately takes some -time. If you experience a segfault, please report it. As a work-around, you can -compile rsyslog without multi-threading:
-./configure --disable-pthreads
-make clean
-make
-make install
This somewhat reduces the ability to handle large message bursts, but even in -single-threaded mode rsyslogd offers great performance (just think that stock -sysklogd has always been using a single thread, only).
-Sysklogd does not forward remotely received messages to other network -destination except when the -h option is given. This code is currently defunct. -No matter if -h is specified or not, messages are ALWAYS forwarded. It is -currently under review if the sysklogd's functionality is actually needed. -Please see my -blog -post on this topic for further detail.
If multiple templates with the SAME name are created, all but the first definition is IGNORED. So you can NOT (yet) replace a @@ -46,10 +23,6 @@ names...).
This format is actually not 100% compatible with stock syslogd - the date is missing. Will be fixed soon and can also be fixed just via the proper template. Anyone up for this? ;)
-Currently, SIGPIPE is ignored. This is necessary to handle broken TCP - connections. We should further look into this issue and see which other - ways exist to handle the situation.
If multiple instances are running on a single machine, the one with the -r switch must start first. Also, UDP-based syslog forwarding between the diff --git a/doc/features.html b/doc/features.html index 2899cd76..c71194dc 100644 --- a/doc/features.html +++ b/doc/features.html @@ -53,36 +53,12 @@ is going on, you can also subscribe to the feature -request tracker at sourceforge.net. This tracker has things typically within +feature +request tracker at our bugzilla. This tracker has things typically within reach of implementation. Users are encouraged to submit feature requests there -(or via our forums). If we like them but they look quite long-lived (aka "not -soon to be implemented"), they will possibly be migrated to this list here and -at some time moved back to the sourceforge tracker.
-To see when each feature was added, see the rsyslog change log (online only).
-- cgit From 1a4ea8dc01a946ad48a0e85808d3e09d047c98d3 Mon Sep 17 00:00:00 2001 From: Rainer GerhardsThis page reflects the status as of 2008-02-12.
+This page reflects the status as of 2008-03-12.
development: 3.11.0 - -change log - -download
-Be sure to read the
-rsyslog v3 compatibility document!
+
development: 3.12.1 - +change +log - +download
+If you used version 2, be sure to read the rsyslog v3
+compatibility document!
Documentation for 3.x is currently sparse. If you need assistance, please
post in the rsyslog forums!
stable: 2.0.2 - change log - -download
+stable: 2.0.3 - change log - +download
Thankfully, a number of folks have begin to build packages and help port
--
cgit
From a2f31852b1467a2e9672ccd8d06a2139f5030942 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards Properties starting with a $-sign are so-called system properties. These do
diff --git a/msg.c b/msg.c
index 5b211b8a..16180e56 100644
--- a/msg.c
+++ b/msg.c
@@ -1243,7 +1243,7 @@ char *textpri(char *pRes, size_t pResLen, int pri)
* can not allocate memory, it returns a NULL pointer.
* Added 2007-07-10 rgerhards
*/
-typedef enum ENOWType { NOW_NOW, NOW_YEAR, NOW_MONTH, NOW_DAY, NOW_HOUR, NOW_MINUTE } eNOWType;
+typedef enum ENOWType { NOW_NOW, NOW_YEAR, NOW_MONTH, NOW_DAY, NOW_HOUR, NOW_HHOUR, NOW_QHOUR, NOW_MINUTE } eNOWType;
#define tmpBUFSIZE 16 /* size of formatting buffer */
static uchar *getNOW(eNOWType eNow)
{
@@ -1272,6 +1272,12 @@ static uchar *getNOW(eNOWType eNow)
case NOW_HOUR:
snprintf((char*) pBuf, tmpBUFSIZE, "%2.2d", t.hour);
break;
+ case NOW_HHOUR:
+ snprintf((char*) pBuf, tmpBUFSIZE, "%2.2d", t.hour / 30);
+ break;
+ case NOW_QHOUR:
+ snprintf((char*) pBuf, tmpBUFSIZE, "%2.2d", t.hour / 15);
+ break;
case NOW_MINUTE:
snprintf((char*) pBuf, tmpBUFSIZE, "%2.2d", t.minute);
break;
@@ -1424,6 +1430,16 @@ char *MsgGetProp(msg_t *pMsg, struct templateEntry *pTpe,
return "***OUT OF MEMORY***";
} else
*pbMustBeFreed = 1; /* all of these functions allocate dyn. memory */
+ } else if(!strcmp((char*) pName, "$HHOUR")) {
+ if((pRes = (char*) getNOW(NOW_HHOUR)) == NULL) {
+ return "***OUT OF MEMORY***";
+ } else
+ *pbMustBeFreed = 1; /* all of these functions allocate dyn. memory */
+ } else if(!strcmp((char*) pName, "$QHOUR")) {
+ if((pRes = (char*) getNOW(NOW_QHOUR)) == NULL) {
+ return "***OUT OF MEMORY***";
+ } else
+ *pbMustBeFreed = 1; /* all of these functions allocate dyn. memory */
} else if(!strcmp((char*) pName, "$MINUTE")) {
if((pRes = (char*) getNOW(NOW_MINUTE)) == NULL) {
return "***OUT OF MEMORY***";
--
cgit
From a628d02d9ff9d630119338e82007282b02d6196d Mon Sep 17 00:00:00 2001
From: Rainer Gerhards $DAY The current day of the month (2-digit)
+$HOUR The current hour in military (24 hour) time
(2-digit)
+
+$HHOUR
+The current half hour we are in. From minute 0 to 29,
+this is always 0 while
+from 30 to 59 it is always 1.
+
+
+$QHOUR
+The current quarter hour we are in. Much like $HHOUR, but values
+range from 0 to 3 (for the four quater hours that are in each hour)
+
$MINUTE The current minute (2-digit)
Visit the rsyslog status page to obtain current diff --git a/doc/professional_support.html b/doc/professional_support.html new file mode 100644 index 00000000..7f5e8371 --- /dev/null +++ b/doc/professional_support.html @@ -0,0 +1,57 @@ + +
+Professional Support is offered by Adiscon, the company +that sponsors rsyslog development. For details, please contact Adiscon Sales.
+ +Purchase rsyslog support directly from the source. This +contract provides priority email support. It is a great option if you +need to provide proof of software support in your organization. This +contract provides
+Under this contract, fixes for old rsyslog releases will be +provided / created, provided that it is possible to do that with the +code base in question. Phone support is not included.
Creating rsyslog config files is easy - but if you would like +to have that extra feature and have no time to do it, this service is +for you. Important: BEFORE you purchase this service, contact us and +inquire (via info@adiscon.com) +whether or not your desired result can be achieved via rsyslog. Once +this is clear, order the service and we will ship a custom-made +configuration file within 5 working days (at latest, most often much +faster). For security reasons, we will not put passwords into the +configuration file, but will place easy to read comments in the places +where you need to put them in. The agreement is governed under German +law. You may also purchase this service if you would like to have your +own configuration file reviewed, e.g. for auditing purposes.
All agreements are +governed under German law. +
+ +This documentation is part of the
+rsyslog
+project.
+Copyright © 2008 by Rainer
+Gerhards and
+Adiscon.
+Released under the GNU GPL version 2 or higher.
This page reflects the status as of 2008-03-12.
+This page reflects the status as of 2008-03-27.
development: 3.12.1 - -change +p>development: 3.12.4 - +change log - -download
+downloadIf you used version 2, be sure to read the rsyslog v3
compatibility document!
-Documentation for 3.x is currently sparse. If you need assistance, please
-post in the rsyslog forums!
stable: 2.0.3 - change log - -download
+Documentation for 3.x is currently partly sparse. If you need +assistance, please +post in +the rsyslog forums! +stable: 2.0.4 - change log - +download
Thankfully, a number of folks have begin to build packages and help port
--
cgit
From 6b9369c95f8dab6571ae508311a6318bddfd7cc9 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards