./sysutils/rsyslog-pgsql, Enhanced syslogd for Unix - the pgsql module

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 8.30.0, Package name: rsyslog-pgsql-8.30.0, Maintainer: filip

rsyslog module for logging into PostgreSQL databases.


Required to run:
[databases/postgresql92-client] [sysutils/rsyslog] [textproc/libfastjson]

Required to build:
[textproc/py-docutils] [devel/libuuid] [lang/python27] [sysutils/liblogging] [devel/libestr] [pkgtools/cwrappers]

Master sites:

SHA1: 59248ac00f5dd27a32bcb979cfa2bc6970f3e8aa
RMD160: 5c394a8d5bfbb7d56287c57c0a51bff9972b0b0d
Filesize: 2410.375 KB

Version history: (Expand)


CVS history: (Expand)


   2016-10-20 12:05:11 by Filip Hajny | Files touched by this commit (6) | Package updated
Log message:
Update sysutils/rsyslog to 8.22.0.

Version 8.22.0 [v8-stable] 2016-10-04
- ompgsql: add template support
  Thanks to Radu Gheorghe for implementing this.
- generate somewhat better error message on config file syntax error
  a common case (object at invalid location) has received it's own error
  message; for the rest we still rely on the generic flex/bison handler
- bugfix:omhiredis reconnects after failure
  previously it could loose messages under such conditions.
  Thanks to Bob Gregory for the patch.
- general cleanup and code improvement
  mostly guided by compiler warnings induced by newer opensuse builbot
  environment
------------------------------------------------------------------------------
Version 8.21.0 [v8-stable] 2016-08-23
- CHANGE OF BEHAVIOUR:
  by default, internal messages are no longer logged via the internal
  bridge to rsyslog but via the syslog() API call [either directly or
  via liblogging). For the typical single-rsyslogd-instance installation this
  is mostly unnoticable (except for some additional latency). If multiple
  instances are run, only the "main" (the one processing system log \ 
messages)
  will see all messages. To return to the old behaviour, do either of those
  two:
  1) add in rsyslog.conf:
     global(processInternalMessages="on")
  2) export the environment variable RSYSLOG_DFLT_LOG_INTERNAL=1
     This will set a new default - the value can still be overwritten via
     rsyslog.conf (method 1). Note that the environment variable must be
     set in your **startup script**.
  For more information, please visit
  http://www.rsyslog.com/rsyslog-error-re … -improved/
- slightly improved TLS syslog error messages
- queue subsystem: improved robustness
  The .qi file is now persisted whenever an existing queue file is fully
  written and a new file is begun. This helps with rsyslog aborts, including
  the common case where the OS issues kill -9 because of insufficiently
  configured termination timout (this is an OS config error, but a frequent
  one). Also, a situation where an orphaned empty file could be left in the
  queue work directory has been fixed. We expect that this change causes
  fewer permanent queue failures.
- bugfix: build failed on some platforms due to missing include files
   2016-10-09 23:42:04 by Thomas Klausner | Files touched by this commit (110)
Log message:
Recursive bump for all users of pgsql now that the default is 95.
   2014-09-05 09:15:41 by Filip Hajny | Files touched by this commit (39)
Log message:
Import rsyslog-8.4.0 as sysutils/rsyslog* (based on wip/rsyslog8).

Rsyslog is an enhanced syslogd supporting, among others, MySQL,
PostgreSQL, failover log destinations, syslog/tcp, fine grain
output format control, high precision timestamps, queued operations
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.