On 12/05/2012 01:21 AM, Angus Salkeld wrote:
> On 04/12/12 20:08 +0100, Fabio M. Di NItto wrote:
>> On 12/04/2012 05:10 PM, Dan Frincu wrote:
>>> Hi,
>>>
>>> Using corosync 1.4.2 (debian backports) and have noticed that if one
>>> messes up corosync.conf in the logging section it still works, but not
>>> as expected.
>>>
>>> For example I had
>>>
>>> logging {
>>> fileline: off
>>> to_stderr: yes
>>> to_logfile: yes
>>> to_syslog: /var/log/corosync/corosync.log
>>> to_syslog: no
>>> syslog_facility: daemon
>>> debug: off
>>> timestamp: on
>>> logger_subsys {
>>> subsys: AMF
>>> debug: off
>>> tags: enter|leave|trace1|trace2|trace3|trace4|trace6
>>> }
>>> }
>>>
>>> Used to_syslog twice instead of logfile and to_syslog. Corosync
>>> started without any errors, and without any logs.
>>
>> to_syslog accepts only yes|no. The first entry would set to default (no
>> IIRC) and the second one would override the first entry and set it to
>> "no" (for sure). Default log file is set to
>> /var/log/cluster/corosync.log. If /var/log/cluster doesn't exists, it
>> would fail to open the log file (aka no logs again).
>>
>>>
>>> Probably should bail early, maybe do some syntax checking.
>>>
>>> Just saying.
>>
>> Patch? ;)
>>
>> The idea is nice, there is no doubt about it, but it's almost "mission
>> impossible" given the complexity (and not just for logging). Not sure
>> maybe Jan has an idea how to fix it easily.
>
> Have augeas run the parser over it in the init script?
>
it might be an option depending on how big the dependency is.
> I have to say the output is not particularly user friendly.
> But it does check the syntax, and it can be figured out.
Right, we need at least to get a decent output from it, or parse it for
the final users.
Fabio
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
