2015-02-03 18:32 GMT+01:00 David Lang <[email protected]>:

> On Tue, 3 Feb 2015, Michael Biebl wrote:
>
>  2015-02-03 10:13 GMT+01:00 Rainer Gerhards <[email protected]>:
>>
>>> 2015-02-03 0:30 GMT+01:00 David Lang <[email protected]>:
>>>
>>>
>>>> On Mon, 2 Feb 2015, Otis Gospodnetic wrote:
>>>>
>>>>  Hi,
>>>>
>>>>>
>>>>> Just installed the very latest 8.7.0 on one machine and spotted this in
>>>>> the
>>>>> log:
>>>>>
>>>>> Feb  2 23:24:27 logsene-reports rsyslogd-2207: error during parsing
>>>>> file
>>>>> /etc/rsyslog.conf, on or before line 55: warnings occured in file
>>>>> '/etc/rsyslog.conf' around line 55 [try http://www.rsyslog.com/e/2207
>>>>> ]
>>>>>
>>>>>
>>>>>
>>>>>  didn't you get the other error message? This is what I see:
>>>
>>> 2015-02-03T10:10:14.076337+01:00 ubuntu1404esp rsyslogd-2184: action '*'
>>> treated as ':omusrmsg:*' - please change syntax, '*' will not be
>>> supported
>>> in the future [v8.8.0.master try http://www.rsyslog.com/e/2184 ]
>>> 2015-02-03T10:10:14.146723+01:00 ubuntu1404esp rsyslogd-2207: error
>>> during
>>> parsing file bluecoat.conf, on or before line 7: warnings occured in file
>>> '/bluecoat.conf' around line 7 [v8.8.0.master try
>>> http://www.rsyslog.com/e/2207 ]
>>>
>>
>>
>> Just in case, this wasn't obvious, please change the line to
>>
>> *.emerg       :omusrmsg:*
>>
>
> Given how many configs are going to have this in it (legacy being
> propogated along), we should look at putting together a script to detect
> this at upgrade time and update the config (at least as this changes from
> being a warning to being an error)
>
>
Just for the records: nothing has changed, it's the same message since v6
(maybe early v7). It's still a warning. But at some points rsyslog is not
so good at differentiating between the two. I am checking code to make sure
this is more inline, this is also needed for the error-exit functions
(several github trackers for that). But I need to review roughly another
580 lines with error messages... ;)

Here is why rsyslog can not accept this part of the legacy eternally (blog
post fom 2011):

http://blog.gerhards.net/2011/07/why-omusrmsg-is-evil-and-how-it-is.html

Rainer
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to