Bug fix record of time_send_input_finish
mem limit
Fix a bug where argv[0] was not set correctly.

Haiyan encountered a problem in a CMS application caused by linking failures
because the application was ultimately using argv[0] to look for libraries
(Python modules in this case). Unfortunately, there's is a bug where we assumed
that ld-linux.so does not replace argv[0]. So what we were doing was:

    execve('ld-linux.so', ['logical-exe', 'physical-exe', ...], [...]);

However, the argv that is ultimately given to the application is:

    ['physical-exe', ...]

what we wanted was:

    ['logical-exe', ...]

When the 'physical-exe' refers to an executable cached by Parrot, this will not
make sense to the application (Python), causing a failure.

Haiyan did most of the work in isolating the cause of this problem.
Removed code that duplicated nvpair_export().
Check envlist is not null before exporting!
Merge pull request #645 from dthain/master

Fix Crash if Environment Null
Merge branch 'master' of github.com:cooperative-computing-lab/cctools
1. Use docker "--rm" option to remove container instead of c subprocess
2. Create "container_mode" option for work_queue worker. i.e. container_mode = NONE | DOCKER | UMBRELLA | ...
3. Remove the "WORKER_MODE_DOCKER" option from "worker_mode"
Use debian as default docker image