Correct.
If we are using syntax which is only valid in bash extensions, we should point to bash and not to sh.
Rainer
Gesendet:Montag, 03. Februar 2014 um 18:16 Uhr
Von:Sherwood McGowan sherwood.mcgo...@gmail.com
An:pacemaker@oss.clusterlabs.org
Betreff:Re: [Pacemaker] Kamailio managed by
-Ursprüngliche Nachricht-
Von:Loick Pelet lpe...@inverse.ca
If anyone has an idea to help me, thank you in advance.
You can set a colocation with negative infinite value, means that ressources
will never run on the same host together.
colocation db_not_with_suricata -inf: res_mysql
Loick,
I think that the score values you set in your location rules are meant to do
that, arent they ?
Regards,
Pascal.
De : Loick Pelet [mailto:lpe...@inverse.ca]
Envoyé : mardi 4 février 2014 14:07
À : The Pacemaker cluster resource manager
Objet : [Pacemaker] [pacemaker] 1 resource
Thanks Stefan,
I’ll try that.
regards.
Loick
On Feb 4, 2014, at 8:40 AM, Stefan Bauer stefan.ba...@cubewerk.de wrote:
-Ursprüngliche Nachricht-
Von: Loick Pelet lpe...@inverse.ca
If anyone has an idea to help me, thank you in advance.
You can set a colocation with negative
On 3 Feb 2014, at 11:34 pm, Frank Brendel frank.bren...@eurolog.com wrote:
As far as I know, Pacemaker does not parse STDOUT but it keeps STDERR
for logging.
Experts correct me if I am wrong.
You are correct
[snip]
Does nobody have an idea? I checked this link:
On 05.02.2014 04:06, Andrew Beekhof wrote:
On 3 Feb 2014, at 11:34 pm, Frank Brendel frank.bren...@eurolog.com wrote:
As far as I know, Pacemaker does not parse STDOUT but it keeps STDERR
for logging.
Experts correct me if I am wrong.
You are correct
[snip]
Does nobody have an idea? I
Hi All,
We tried to set sequential attribute of resource_set of colocation in true in
crmsh.
We tried the next method, but true was not able to set it well.
-
[pengine]# crm --version
2.0 (Build 7cd5688c164d2949009accc7f172ce559cadbc4b)
- Pattern 1 -
colocation
Please could you post the init script, the resource configuration and
the pacemaker version?
Frank
The return code of service ipsec status is always 0 yet crm status
shows the failure:
p_ipsec_monitor_15000 on node02 'not running' (7): call=113,
status=complete, last-rc-change='Mon Jan 27
