search for: testdump

...allows the specification of a callback routine and an opaque argument block. The existing dumpcore routine is modified to use the callback for all write operations and to turn the single seek into a small write (it''s for page alignment). I''ve also included a small test routine, testdump.c, which drives both APIs and allows writing core to either a local disk file or across a network. And, I''ve included a sample network "catcher" program that receives a cross-network dump from testdump. And, good news, this probably ends my current hacking/interest in xc_domain...

...or S-PLUS 5.x > and 6.x you may need to use |dump(..., oldStyle=T)|, and to read in > very large objects it may be preferable to use the dumpfile as a batch > script rather than use the |source| function.* (from "R Data Import/Export," pg. 15) An example: > source("testdump") Error in parse(file, n, text, prompt) : syntax error on line 1895 where the data on line 1895 - and other lines causing this - have embedded spaces, such as the following: [line 1895] Johnson Partners LLC I can't seem to find any options for either the SPlus dump, or R source(),...

...esent location. Any assistance would be greatly appreciated. I should be able to provide log files in about 12 hours. At this moment, loadavgs on each node are 0.00 to 0.09. Here is a test write and associated iostat -xm 5 output. Previously I was obtaining > 90MB/s: $ dd if=/dev/zero of=/home/testdump count=1000 bs=1024k ...and associated iostat output: avg-cpu: %user %nice %system %iowait %steal %idle 0.10 0.00 0.43 12.25 0.00 87.22 Device: rrqm/s wrqm/s r/s w/s rMB/s wMB/s avgrq-sz avgqu-sz await svctm %util sda 0.00 1....

...quot; [13] "rescale" "utm2lincol" You can use lsf() to save your functions to a file: > save(list=lsf(), file="Rfunctions.rda") 9. Actually, it's more usual to save functions in text format, which you can do with: > dump(list=lsf(),file="testdump.R") But you cannot use either load() or attach() with files created by dump(). Instead, you must use source() > source("testdump.R") but beware that source() will create the functions in your workspace. I've not found any way to direct source() to another position. 10.So...

Any progress here? Does anyone know if this will be fixed in 7.1 latest, or should we start looking for different backup solution (in this case I would suggest to remove dump from the source tree - having a backup tool that doesn't work is worse than having none). After upgrading we basically cannot backup our servers. Shouldn't this issue be on