Atin Mukherjee wrote:
> To debug the volume-status.t failure in netbsd for the regression run
> [1] I was trying to download the log archive however was not able to
> connect to the machine.
You can connect as user jenkins with the usual password.
But here it is:
http://ftp.espci.fr/shadow/manu
Missed out the link, here it goes
[1]
http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/662/consoleFull
~Atin
On 01/16/2015 10:38 AM, Atin Mukherjee wrote:
> Hi Emmanuel,
>
> To debug the volume-status.t failure in netbsd for the regression run
> [1] I was trying to download t
Hi Emmanuel,
To debug the volume-status.t failure in netbsd for the regression run
[1] I was trying to download the log archive however was not able to
connect to the machine.
Can you please help me on getting the log file, is the server not
responsive?
~Atin
On 01/15/2015 10:53 PM, Xavier Hernandez wrote:
Hi,
currently eager locking is implemented by checking the open-fd-count
special xattr for each write. If there's more than one open on the
same file, eager locking is disabled to avoid starvation.
This works quite well for file writes, but ma
Thanks Jeff and Kaleb for providing a good insight.
At least in Gluster code I have not come across any use of go to other than
forward and out.
On 16-Jan-2015, at 12:21 am, Jeff Darcy wrote:
>> Since the goto idiom that Gluster uses generates the same code — which
>> is what matters — I ga
At least two users [1] are reporting that the operating version [2]
should be 30600 in 3.6.1 and not 30601 as convention might have it.
I don't care either way actually, but I just wanted to confirm this
isn't a bug in 3.6.1 so that I can patch puppet-gluster correctly.
Cheers,
James
[1]
15:05
> Since the goto idiom that Gluster uses generates the same code — which
> is what matters — I gave up my short-lived battle for not using it.
One handy rule of thumb is based on whether a "goto" is forward or back,
in (to a loop or other control contruct) or out. Forward and out are
generally OK
On 01/15/2015 08:02 AM, Nagaprasad Sathyanarayana wrote:
On 15-Jan-2015, at 5:38 pm, Vijay Bellur wrote:
On 01/15/2015 12:13 PM, Nagaprasad Sathyanarayana wrote:
In a quest to find why good programmers are wary of the "Go To"
statement, came across this interesting article by /Edsger W. Dijkst
Hi,
currently eager locking is implemented by checking the open-fd-count
special xattr for each write. If there's more than one open on the same
file, eager locking is disabled to avoid starvation.
This works quite well for file writes, but makes eager locking unusable
for other request type
Thanks Vijay for sharing these. Very informative.
Thanks
Naga
> On 15-Jan-2015, at 5:38 pm, Vijay Bellur wrote:
>
>> On 01/15/2015 12:13 PM, Nagaprasad Sathyanarayana wrote:
>> In a quest to find why good programmers are wary of the "Go To"
>> statement, came across this interesting article b
On 01/15/2015 12:13 PM, Nagaprasad Sathyanarayana wrote:
In a quest to find why good programmers are wary of the "Go To"
statement, came across this interesting article by /Edsger W. Dijkstra/ .
http://www.u.arizona.edu/~rubinson/copyright_violations/Go_To_Considered_Harmful.html.
goto statem
11 matches
Mail list logo
