I'll take up documenting the options framework. I'd like take up graph
and dict, if Jeff doesn't mind.
Also, I think we should be aiming to document the complete API
provided by these components instead of just the data structure. That
would be more helpful to everyone IMO.
~kaushal
On Wed, Jul
On Tue, Jul 15, 2014 at 04:39:39PM +0530, Pranith Kumar Karampuri wrote:
hi,
Please respond if you guys volunteer to add documentation for
any of the following things that are not already taken.
client_t - pranith
integration with statedump - pranith
mempool - Pranith
On 07/16/2014 11:57 AM, Kaushal M wrote:
I'll take up documenting the options framework. I'd like take up graph
and dict, if Jeff doesn't mind.
Also, I think we should be aiming to document the complete API
provided by these components instead of just the data structure. That
would be more
Harshavardhana har...@harshavardhana.net wrote:
Its pretty much the same on FreeBSD, i didn't spend much time debugging
it. Let me do it right away and let you know what i find.
Right. Once you will have this one, I have Linux-specific truncate and
md5csum replacements to contribute. I do not
Copying gluster-devel@
Thanks for reporting Michael. I guess we need to forward port that old
change. Can you please send out a patch to gerrit?
Thanks!
On 7/16/14, 2:36 AM, 马忠 wrote:
Hi Avati,
I tried to build the latest glusterfs 3.5.1 on solaris11.1, but
it stopped because of
So here is what i found long email please bare with me
Looks like the management daemon and these other daemons
eg: brick, nfs-server, gluster self-heal daemon
They work in non-blocking manner, as in notifying back to Gluster
management daemon when they are available and when they are not. This
Hi Avra,
Just clarifying things here,
1) When testing with the setup provide by Justin, I found the only place where
bug-1112559.t failed was after the failure mgmt_v3-locks.t in the previous
regression run. The mail attached with the previous mail was just an
OBSERVATION and NOT an INFERENCE
