set c1_pid [spawn /bin/sh -c "$client_binary -f $masterchunks -p $nodes -c $empty -i 1 -m 1 -d $debug | tee first.output"]Another way to accomplish this, but without causing the extra debugging output to confuse the check script, is to use the debugging macros we provided (which spit debugging output to stderr instead of stdout). You can also redirect just stderr to a file:
set c1_pid [spawn /bin/sh "$client_binary -f $masterchunks -p $nodes -c $empty -i 1 -m 1 -d $debug 2> first.stderr"]
In both of these cases, we've had to modify the spawn to run a shell which then executes the specified command. Output redirection of this sort is a shell function, and by default, spawn just executes the requested program directly.
limit see the limits unlimit coredumpsize limit coredumpsize unlimited unlimit it In bash: ulimit -c to see the coredump size limit ulimit -c unlimited to unlimit it
To find the process ID:
ps auxww | grep <program name>
You can't run the checkpoint script on the netclass machines because the expect binary isn't compiled for that environment. However, you can still run your programs there and tcpdump them, if you don't have a linux / bsd / macos x machine of your own to run on. To tcpdump problems with spiffy, you'll want to supply the -i lo (linux) or -i lo0 (bsd, mac) flag to tell tcpdump to sniff on the loopback interface.