search for: resursive

It appears that in version 0.23 of puppet that how I am trying to create directories is nor working. If I have a snippet like this: # Set up the images file {"$git_web_image_location": ensure => directory, recurse => true } which becomes: file {"/var/www/html/images/git": ensure => directory,

...and enforce this order at final link (link-exec/shared-lib) stage. >> >> Anyway, I try to ignore all these problems, and try to perform partition >> via following steps. Maybe we have some luck on some platforms: >> >> o. DFS the call-graph, ignoring the self-resursive edges, if freq is >> available, prioritizing the edges (i.e. corresponding to call-sites) >> such that frequent edges are visited first. >> >> o. Cut the DFS spanning tree obtained from the previous step bottom-up, >> Each cut/partition contains reason...

...is order at final link (link-exec/shared-lib) stage. >>> >>> Anyway, I try to ignore all these problems, and try to perform partition >>> via following steps. Maybe we have some luck on some platforms: >>> >>> o. DFS the call-graph, ignoring the self-resursive edges, if freq is >>> available, prioritizing the edges (i.e. corresponding to call-sites) >>> such that frequent edges are visited first. >>> >>> o. Cut the DFS spanning tree obtained from the previous step bottom-up, >>> Each cut/partitio...

...MAP_SHADOW_TO needs to be either a drive letter that isn't @REM currently in use, or an empty directory @REM eg. x: or c:\temp\shadowcopy @REM set SHADOW_DRIVE_LETTER=D: set MAP_SHADOW_TO=X: @REM @REM Create the shadow copy - and generate env variables into a temporary script. @REM Then resursively come back into this script. set CALLBACK_SCRIPT=%~dpnx0 set TEMP_GENERATED_SCRIPT=GeneratedTempScript.cmd @echo ...Create the shadow copy... vshadow.exe -nw -p -script=%TEMP_GENERATED_SCRIPT% -exec=%CALLBACK_SCRIPT% %SHADOW_DRIVE_LETTER% del /f %TEMP_GENERATED_SCRIPT% @goto :EOF :IS_...

I noticed today, that rsync does not appear to set the permissions on a directory until all of the contents are in place. this only really becomes noticeable and/or problematic when rsync'ing a large directory tree as root to a new, empty, location. For example, if you have the following tree: /foo /bar /file1 /file2 /baz /file3 /file4 When rsyncing this tree to another

...t obj/fake-obj, > and enforce this order at final link (link-exec/shared-lib) stage. > > Anyway, I try to ignore all these problems, and try to perform partition > via following steps. Maybe we have some luck on some platforms: > > o. DFS the call-graph, ignoring the self-resursive edges, if freq is > available, prioritizing the edges (i.e. corresponding to call-sites) > such that frequent edges are visited first. > > o. Cut the DFS spanning tree obtained from the previous step bottom-up, > Each cut/partition contains reasonable # of functions, an...

In another thread recursive snapshot creation was found atomic so that it is done quickly, and more important, all at once or nothing at all. Do you know if recursive destroying and renaming of snapshots are atomic too? Regards Henrik Heino

I''ve spent the past while researching this but I''m just not finding a solution. I''ve been trying to get my xen kernel booting on a pretty much stock CentOS 4.4 installation. I installed Xen from src rpm and installed all the requisite software and I''m sure it''s with the ram disk but I can''t figure out how to resolve this. With a stock kernel

...der of the pristine input obj/fake-obj, and enforce this order at final link (link-exec/shared-lib) stage. Anyway, I try to ignore all these problems, and try to perform partition via following steps. Maybe we have some luck on some platforms: o. DFS the call-graph, ignoring the self-resursive edges, if freq is available, prioritizing the edges (i.e. corresponding to call-sites) such that frequent edges are visited first. o. Cut the DFS spanning tree obtained from the previous step bottom-up, Each cut/partition contains reasonable # of functions, and the aggregate...

...obj/fake-obj, > and enforce this order at final link (link-exec/shared-lib) stage. > > Anyway, I try to ignore all these problems, and try to perform partition > via following steps. Maybe we have some luck on some platforms: > > o. DFS the call-graph, ignoring the self-resursive edges, if freq is > available, prioritizing the edges (i.e. corresponding to call-sites) > such that frequent edges are visited first. > > o. Cut the DFS spanning tree obtained from the previous step bottom-up, > Each cut/partition contains reasonable # of functions,...