On 10/04/2013, at 2:21 PM, Andrei Belov defana...@gmail.com wrote:
On Apr 10, 2013, at 2:06 , Andrew Beekhof and...@beekhof.net wrote:
On 09/04/2013, at 4:13 PM, Andrei Belov defana...@gmail.com wrote:
Hello pacemaker users,
I noticed that neither -p nor -f option does not make any
Hello pacemaker users,
I noticed that neither -p nor -f option does not make any sense for
pacemakerd -
pid_file is never used, and f option marked as Legacy.
Is the ability to run as a daemon disappeared completely?
Also I'd like to know if there are any reasons to worry about the following:
On 09/04/2013, at 4:13 PM, Andrei Belov defana...@gmail.com wrote:
Hello pacemaker users,
I noticed that neither -p nor -f option does not make any sense for
pacemakerd -
pid_file is never used, and f option marked as Legacy.
Is the ability to run as a daemon disappeared completely?
On Apr 10, 2013, at 2:06 , Andrew Beekhof and...@beekhof.net wrote:
On 09/04/2013, at 4:13 PM, Andrei Belov defana...@gmail.com wrote:
Hello pacemaker users,
I noticed that neither -p nor -f option does not make any sense for
pacemakerd -
pid_file is never used, and f option marked
On Apr 10, 2013, at 8:21 , Andrei Belov defana...@gmail.com wrote:
On Apr 10, 2013, at 2:06 , Andrew Beekhof and...@beekhof.net wrote:
On 09/04/2013, at 4:13 PM, Andrei Belov defana...@gmail.com wrote:
Hello pacemaker users,
I noticed that neither -p nor -f option does not make any
Hello all, Andrew,
I am performing tests against pacemaker from commit
7a9bf21cfc993530812ee43bde8c5af2653c1fa6 and for some reason it does not
want to daemonize:
root@Cluster-Server-1:~/crmsh# pacemakerd -V
Could not establish pacemakerd connection: Connection refused (111)
info:
Mysteriously the problem is gone, so I guess I screwed up the installation
at some point.
On Fri, Sep 14, 2012 at 12:32 PM, Borislav Borisov
borislav.v.bori...@gmail.com wrote:
Hello all, Andrew,
I am performing tests against pacemaker from commit
7a9bf21cfc993530812ee43bde8c5af2653c1fa6
