1 |
Hi Jarry, |
2 |
|
3 |
I work for BalaBit, the developer of syslog-ng, and am the maintainer |
4 |
of the syslog-ng docs. |
5 |
You are right, the program-override option is missing from the |
6 |
documentation of the file source, but it should work anyway. |
7 |
We did a quick test and it was working on our Ubuntu machines (tested |
8 |
with syslog-ng 3.02a), both on kernel messages and also on custom |
9 |
files containing log messages. |
10 |
Which version of syslog-ng are you running? Are the messages in the file in |
11 |
correct syslog format, or do they have some custom format? |
12 |
|
13 |
If the problem persists, could you open a ticket in the syslog-ng bugzilla at |
14 |
https://bugzilla.balabit.com/? |
15 |
|
16 |
Regards, |
17 |
|
18 |
Robert Fekete |
19 |
|
20 |
|
21 |
Hi, |
22 |
as syslog-ng 3.0.x became stable, all my servers updated |
23 |
to it from 2.1.4, but I have a problem with configuration: |
24 |
|
25 |
In 2.x I used "log_prefix()" option for "file()" source. |
26 |
When I tried to start syslog-ng 3.x it complained about |
27 |
"log_prefix()" being deprecated, and said I have to use |
28 |
"program_override()" instead. |
29 |
|
30 |
I modified syslog-ng.conf, but it does not work at all. |
31 |
It simply acts as if there was no "program_override()" |
32 |
option in "file()" source. |
33 |
|
34 |
I checked syslog-ng-v3.0-guide-admin-en.pdf and found this: |
35 |
"log_prefix()" really *is* deprecated, but it seems to me |
36 |
that "program_override()" was not implemented in "file()" |
37 |
source driver at all! At least, I did not find it as valid |
38 |
option for "file()" source driver in the chapter 8 Reference |
39 |
(in syslog-ng admin guide)... |
40 |
|
41 |
How can I fix this? I definitelly need that "log_prefix()" |
42 |
(or "program_override()") option as I use it later for |
43 |
filtering of non-standard log messages on my log-server... |
44 |
|
45 |
Jarry |