Vidar Hokstad

I'm seeing pretty much the same thing. This is on CoreOS 607. On older versions it works fine.

Hi, thanks for this. Looking at it, I'm guessing the text is there but has ended up white on white background. Likely a relatively easy fix - I'll have a...

Finally had a chance to start looking at it. I've spotted a few more issues, so I think as a first step I'm going to try to untangle a few...

I think the backoff in principle is fine, but there ought to be a (relatively low) ceiling on it so it doesn't keep increasing - the benefit of a backoff...

Changing the name is actually the smallest part of the problem - we also need to create a static "slot table" (fast) or hash table (slow, but more flexible) to...

(notice the second call &%eax)

I see this consistently with Consul 0.5.0 (using the progrium/consul image - not yet been able to test with the new image) on CoreOS on AWS. From the consul container:...

These are zombie processes. The issue is almost certainly something that manages to effectively double-fork and that Consul isn't reaping those child processes. The most likely cause is that the...

@krallin very interesting, thanks. @progrium The minimal requirements for an init are truly minimal, so as @krallin said id boils down to if they can easily be done in Go...

@progrium I could resist looking into this, and here's a very, very limited init (even more limited than Suckless Init and certainly much more limited than what @krallin linked to)...