search for: active1

Displaying 5 results from an estimated 5 matches for "active1".

Did you mean: active
2014 Jan 29
0
Re: Looks like blockpull does not accept a subset of the entire chain of backing files
...<- active ------------c1 - d1 Use 'qemu-img rebase -u -b c1 d1' for this tree: root \- a <- b <- c <- d <- active ------------c1 <- d1 Create a blank destination active file wrapping d1, with 'qemu-img create -f qcow2 -o backing_file=d1,backing_fmt=qcow2 active1' for this tree: root \- a <- b <- c <- d <- active ------------c1 <- d1 <- active1 Set up a block mirroring, and pivot over to the new chain once it is stable, with 'virsh blockcopy $dom active --dest active1 --shallow --reuse-external --wait --pivot', for this...
2014 Jan 29
4
Looks like blockpull does not accept a subset of the entire chain of backing files
Hello If I'm not terribly mistaken, looks like libvirt 1.2.1 does not provide ability of merging only a subset of the entire chain of backing files. So, if I have a chain like this: root <- a <-b <- c <- d <- active ... and I'd like to obtain a chain like this: root <- c <- d <- active ... looks like it's not supported,
2014 Jan 29
2
Re: Looks like blockpull does not accept a subset of the entire chain of backing files
...1 - d1 > > Use 'qemu-img rebase -u -b c1 d1' for this tree: > root \- a <- b <- c <- d <- active > ------------c1 <- d1 > > Create a blank destination active file wrapping d1, with 'qemu-img > create -f qcow2 -o backing_file=d1,backing_fmt=qcow2 active1' for this tree: > root \- a <- b <- c <- d <- active > ------------c1 <- d1 <- active1 > > Set up a block mirroring, and pivot over to the new chain once it is > stable, with 'virsh blockcopy $dom active --dest active1 --shallow > --reuse-external -...
2007 Oct 16
3
Controller iterating through returned records and appending to each
I have a controller that gets a list of employees (which has an "include => [:salaries, :incentives, :billablegoals, :reviews]"). I then need it to iterate through each employee and determine their current active goal based on the "effective date." After playing around with it a bunch, I got the following to work. Only problem is that if I remove the "@employees.each {
2006 Nov 21
1
NEWBIE: Help explaining use of lm()?
...kage:survival : lung > data(zelazo) > head(zelazo) $active [1] 9.00 9.50 9.75 10.00 13.00 9.50 $passive [1] 11.00 10.00 10.00 11.75 10.50 15.00 $none [1] 11.50 12.00 9.00 11.50 13.25 13.00 $ctr.8w [1] 13.25 11.50 12.00 13.50 11.50 > walk <- unlist(zelazo) > walk active1 active2 active3 active4 active5 active6 passive1 passive2 9.00 9.50 9.75 10.00 13.00 9.50 11.00 10.00 passive3 passive4 passive5 passive6 none1 none2 none3 none4 10.00 11.75 10.50 15.00 11.50 12.00 9.00 11.50 none5 none...