Hi
I have not built master for a while, and now find GNU specific extensions
that are not portable. Since it is not the first time I address them,
I would like to send a reminder about it:
1) bash-specific syntax
Do not write:
test $foo == bar
But instead write:
test $foo = bar
Should we create bugs for each of these, and divide-and-conquer?
- Luis
On 05/15/2014 10:27 AM, Niels de Vos wrote:
On Thu, May 15, 2014 at 06:05:00PM +0530, Vijay Bellur wrote:
On 04/30/2014 07:03 PM, Justin Clift wrote:
Hi us,
Was trying out the GlusterFS regression tests in Rackspace VMs
On 05/15/2014 07:57 PM, Niels de Vos wrote:
On Thu, May 15, 2014 at 06:05:00PM +0530, Vijay Bellur wrote:
On 04/30/2014 07:03 PM, Justin Clift wrote:
Hi us,
Was trying out the GlusterFS regression tests in Rackspace VMs last
night for each of the release-3.4, release-3.5, and master branches.
On Thu, May 15, 2014 at 5:49 PM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
hi,
In the latest build I fired for review.gluster.com/7766 (
http://build.gluster.org/job/regression/4443/console) failed because of
spurious failure. The script doesn't wait for nfs export to be
- Original Message -
From: Ravishankar N ravishan...@redhat.com
To: Pranith Kumar Karampuri pkara...@redhat.com, Gluster Devel
gluster-devel@gluster.org
Sent: Friday, May 16, 2014 7:15:58 AM
Subject: Re: [Gluster-devel] Need inputs for command deprecation output
On 05/16/2014
Hey Gluster. I realized that things might have changed at some point,
so I was hoping someone could help me get this straight.
Who can enumerate or provide reference to a list of all the files that
should have specific SELinux attributes in Gluster, and what each of
them is.
Currently,
Due to some weird automation things, I noticed the following:
Given a cluster of hosts A,B,C,D
It turns out that if you restart glusterd on host B while you are
running volume create on host A, this can cause host B to be borked.
This means: glusterd will refuse to start, and the only fix I
Hi,
When automatically building volumes, a volume create failed:
volume create: puppet: failed: Commit failed on
----. Please check log file for
details.
The funny thing was that 'gluster volume info' showed a normal looking
volume, and starting it worked fine.
