On Fri, Jan 4, 2013 at 10:13 PM, Michal Fiala wrote:
> So we use old version of pacemaker? What version should we update to?
1.1.8 is pretty good.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pac
So we use old version of pacemaker? What version should we update to?
On 01/04/2013 11:57 AM, Andrew Beekhof wrote:
> On Fri, Jan 4, 2013 at 8:30 PM, Michal Fiala wrote:
>> Hallo,
>>
>> thanks for information. We are using corosync-1.4.4 and
>> pacemaker-1.1.6.1.
>
> Oh, thats the old lrmd. In
On Fri, Jan 4, 2013 at 8:30 PM, Michal Fiala wrote:
> Hallo,
>
> thanks for information. We are using corosync-1.4.4 and
> pacemaker-1.1.6.1.
Oh, thats the old lrmd. In which case your original assessment could
well be correct.
> Pacemaker is started as a modul by corosync.
>
> corosync loggin
Hallo,
thanks for information. We are using corosync-1.4.4 and
pacemaker-1.1.6.1. Pacemaker is started as a modul by corosync.
corosync loggin option:
logging {
fileline: off
to_stderr: no
to_logfile: no
logfile: /var/log/corosync.log
to_syslog: yes
On Fri, Dec 21, 2012 at 11:16 PM, Michal Fiala wrote:
> Hallo,
>
> we use corosyng logging via syslog (to_logfile: no; to_syslog: yes;
> syslog_facility: local0; debug: on). Some OCF scripts do not use OCF API
> to execute commands. I mean function ocf_run, which capture STDOUT and
> STDERR. For e
Hallo,
we use corosyng logging via syslog (to_logfile: no; to_syslog: yes;
syslog_facility: local0; debug: on). Some OCF scripts do not use OCF API
to execute commands. I mean function ocf_run, which capture STDOUT and
STDERR. For example linbit/drbd uses its own function to execute
do_cmd(), whic
