Ah, and you can also suggest increasing the swap. It would not actually be
used, but the system would be able to commit to the amount of memory
required, if it really had to.
On Jun 3, 2015 1:24 AM, "Gustavo Niemeyer" wrote:
> Hey John,
>
> It's probably an overcommit issue. Even if you don't ha
Hey John,
It's probably an overcommit issue. Even if you don't have the memory in
use, cloning it would mean the new process would have a chance to change
that memory and thus require real memory pages, which the system obviously
cannot give it. You can workaround that by explicitly enabling overc
I can get fork to fail with this script (my laptop has 16GB of RAM for
reference):
package main
import (
"fmt"
"os"
"os/exec"
"sync"
)
const GB = 1024 * 1024 * 1024
func main() {
// allocate!
bigs := make([]*[GB]byte, 14)
for i := range bigs {
bigs[i] = &[GB]byte{}
}
// fork me!
c := exec.Comm
So we're running into this failure mode again at one of our sites.
Specifically, the system is running with a reasonable number of nodes
(~100) and has been running for a while. It appears that it wanted to
restart itself (I don't think it restarted jujud, but I do think it at
least restarted a lo
On Tue, Jun 2, 2015 at 5:57 AM, Katherine Cox-Buday
wrote:
> I think there was an effort to remove this from our code, but I thought I'd
> send out a reminder to check and for personal projects. May the source be
> with you...
code.google.com/p/winsvc is the only one left and there's a patch up
f
If you git clone the new repo into the old path on disk, that should just
work with godeps etc.
On Jun 2, 2015 8:15 AM, "John Meinel" wrote:
> What about old releases, etc? It seems like this is potentially an issue
> if we ever want to build an old release (for reference purposes,
> reproducing
What about old releases, etc? It seems like this is potentially an issue if
we ever want to build an old release (for reference purposes, reproducing a
bug, etc).
Do we at least have a reasonable workaround (grab the code from X move it
to Y, set the version using godeps), etc?
John
=:->
On Tue,
I think there was an effort to remove this from our code, but I thought I'd
send out a reminder to check and for personal projects. May the source be
with you...
-
Katherine
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/lis
Hey folks,
Just wanting to share the knowledge in case I get hit by a bus (and
provide an opportunity for those of you who know more than me to point
out my howling errors) :-)
With the new MAAS (1.8) devices API, to allocate an IP address for a
container we need to know the MAC address of t
