search for: _paths

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

Did you mean: paths
2012 May 30
10
[xen-unstable test] 12988: regressions - FAIL
flight 12988 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12988/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-oldkern 4 xen-build fail REGR. vs. 12979 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-qemuu-win7-amd64 12
2012 Feb 08
0
path enumeration in a graph
...tion of network and graph tools. However, I can't seem to put my finger on the solution to my problem. There are several procedures available in R for finding a shortest path along edges between vertices based on the cost of traversing a link, but my problem is to find _all_ of the _longest _paths between vertices for a critical path method-type computation and others in the future. Aside from brute force searching of all possible paths for the longest and piling up a list of those with the same length, can someone point me to a method that's already been figured out? One that I'...
2009 Nov 05
0
unicorn 0.94.0 - small fixes and new features
...y Do not override Dir.chdir in config files configurator: add "working_directory" directive configurator: working_directory is expanded configurator: set ENV["PWD"] with working_directory, too configurator: working_directory affects pid, std{err,out}_paths configurator: update documentation for working_directory TODO: remove working_directory bit, done Util.reopen_logs: remove needless Range worker: user/group switching for after_fork hooks Fix autoload of Etc in Worker for Ruby 1.9 bin/unicorn: allow RACK_ENV to b...
2012 Aug 14
12
[TESTDAY] xl cpupool-create segfaults if given invalid configuration
# xl cpupool-create ''name="pool2" sched="credit2"'' command line:2: config parsing error near `sched'': syntax error, unexpected IDENT, expecting NEWLINE or '';'' Failed to parse config file: Invalid argument *** glibc detected *** xl: free(): invalid pointer: 0x0000000001a79a10 *** Segmentation fault (core dumped) Looking at the code
2007 May 07
68
Puppet Best Practice
Hello everyone, A long time ago, I posted the Stanford Best Practices and I''ve gone through and updated it today. I''d like to have people go through it and see if we can strip out some Stanford specific stuff and tag this as an official best practice. I think an official best practice will be important as more and more people consider making shareable modules, etc (mostly