My pleasure. Looks like I didn't quite do what I needed though (the hook
script I needed the new var for is a work in progress; just noticed the
var still isn't available in the hook stage I actually need).
Is there any reason I can't try to expand the scope of the new var a bit
so that it is available in more stages (and possibly expand scope of
$dumpdir too)? The only reason I could think of is if you had plans to
allow use of more than one backup target/storeid during a single run of
vzdump (i.e.: this VM is dumped to "backups", that VM is dumped to
"backup2", etc). That would seem to get in the way of bringing the scope
out a level since those values would change as VMs were backed up.
TIA for any insights,
Mark
On 9/11/2013 11:24 PM, Dietmar Maurer wrote:
applied, thanks!
-----Original Message-----
From: Mark Casey [mailto:[email protected]]
Sent: Donnerstag, 12. September 2013 01:22
To: Dietmar Maurer
Subject: Re: [pve-devel] [PATCH] Pass what storage ID is being used to vzdump
hook scripts
I set some git config options and regenerated. Is this one OK?
_______________________________________________
pve-devel mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
