search for: setparams

Hi, Our lustre environment is: 2.6.9-55.0.9.EL_lustre.1.6.3smp I would like to change recovery timeout from default value 250s to something longer I tried example from manual: set_timeout <secs> Sets the timeout (obd_timeout) for a server to wait before failing recovery. We performed that experiment on our test lustre installation with one OST. storage02 is our OSS [root at

Add new commands to manage SR-IOV device. Signed-off-by: Yu Zhao <yu.zhao@intel.com> diff -r b642e39d96cf tools/python/xen/util/pci.py --- a/tools/python/xen/util/pci.py Thu Sep 25 17:41:29 2008 +0100 +++ b/tools/python/xen/util/pci.py Sat Sep 27 01:08:05 2008 -0400 @@ -17,7 +17,7 @@ PROC_PCI_PATH = ''/proc/bus/pci/devices'' PROC_PCI_NUM_RESOURCES = 7

The Wine development release 5.1 is now available. What's new in this release (see below for details): - Support for using LLVM-MinGW as PE cross-compiler. - Better reporting of error location in JScript and VBScript. - Support for relocatable installation of the Winelib tools. - Ellipse drawing in Direct2D. - OLE monikers improvements. - Various bug fixes. The source is

...They retain parameters across calls with different subsets of the cases (this is for distributed computation). They retain early analysis of the problem to speed later computations. I've created an S4 object, and the stylized code looks like this calc <- makeCalculator(a, b, c) calc <- setParams(calc, d, e) calc <- compute(calc) results <- results(calc) The client code (such as that above) must remember to do the assignments, not just invoke the functions. I notice this does not seem to be the usual style, which is more like results <- compute(calc) and possibly using assignment...

The Wine development release 5.0-rc1 is now available. This is the first release candidate for the upcoming Wine 5.0. It marks the beginning of the yearly code freeze period. Please give this release a good testing to help us make 5.0 as good as possible. What's new in this release (see below for details): - Gecko update, with support for running from a global location. - Unicode data

Best fortress support was understandably dropped, but we still use them, and someone else may want the driver I ported to nut-2.0. We also often attach the serial cable from a UPS to a network terminal server, since servers these days don't come with very many serial ports. (They call them "legacy" ports.) I submitted a patch to support these for nut-1.x, and it was rejected

is anybody else having problems with the new java 1.6.0.22 ? i am tried both cortado-ovt-debug and cortado-ovtk-debug - neither seem to work anymore once i installed the new java. once i go back to the old java 21 everything works fine. my jar file downloads for console messages (below) came from: http://downloads.xiph.org/releases/cortado/cortado-ovtk-debug-0.6.0.jar i have included

This patch set adds XSM security labels to useful debugging output locations, and fixes some assumptions that all interrupts behaved like GSI interrupts (which had useful non-dynamic IDs). It also cleans up the policy build process and adds an example of how to use the user field in the security context. Debug output: [PATCH 01/10] xsm: Add security labels to event-channel dump [PATCH 02/10] xsm:

A new intel-gpu-tools quarterly release is available with the following changes: Library changes: - Added helpers for using DRM syncobj. (Jason Ekstrand) - Refactored several i915 helpers into library functions. (Michał Winiarski) - Improved the GPU quiescing code to more thoroughly flush old data and pending work. (Chris Wilson) - Reworked DRM property handling to be more suitable for

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -