Martin Bagge / brother brot...@bsnet.se writes:
On 2013-11-20 15:57, Gergely Nagy wrote:
The file() thing here comes from the system() source. system() is
expanded at run-time, depending on the OS/platform/whatever
syslog-ng is running on.
You can run syslog-ng
Control: tag -1 upstream
I managed to reproduce the problem using a 3.2 kernel, I know how to fix
it, and I'm now working on a patch (it's not trivial to make the fix
nice).
I expect I'll be able to do a 3.5.2 release early next week, and the
package will hit unstable a few hours later.
--
|8]
Andrei POPESCU andreimpope...@gmail.com writes:
On Mi, 20 nov 13, 00:19:49, Martin Bagge / brother wrote:
[...]
[] Starting system logging: syslog-ngUnable to determine how to
monitor this file, follow_freq() unset and it is not possible to poll
it with the current ivykis polling method.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2013-11-20 15:57, Gergely Nagy wrote:
The file() thing here comes from the system() source. system() is
expanded at run-time, depending on the OS/platform/whatever
syslog-ng is running on.
You can run syslog-ng
package: syslog.ng-core
severity: grave
version: 3.5.1-1 http://packages.debian.org/source/testing/syslog-ng
On testing installing syslog-ng-core with no previous syslog-ng config
files you end up in a dpkg failure mess.
It complains about file() directives in the source clauses of the config
Control: reassign -1 syslog-ng-core 3.5.1-1
On Mi, 20 nov 13, 00:19:49, Martin Bagge / brother wrote:
package: syslog.ng-core
severity: grave
version: 3.5.1-1 http://packages.debian.org/source/testing/syslog-ng
On testing installing syslog-ng-core with no previous syslog-ng config
files
6 matches
Mail list logo
