El 17 de noviembre de 2010 12:28, Edier Alberto Zapata Hernández
<edalzap@xxxxxxxxx> escribió:
Hi Jose,
I just finished some tests, trying to get your "error".
The only way to get a job finished before the submit time is that the
submit node's date change When the job is already running.
The finish time is not report from the execute nodes, and if you run
the submit and change the date, the job simply will not start.
So, for some reason your submit node's date "was" changed after your
jobs start.
I hope this help you.
Example:
I start this task (ls -lR /usr) and when condor_q show the job running I ran:
date 11171113
in the submit/master node. And I got same behavior like you.
001 (008.001.000) 11/17 12:13:02 Job executing on host: <192.168.2.12:50208>
...
006 (008.001.000) 11/17 12:13:11 Image size of job updated: 2824
005 (008.001.000) 11/17 11:13:20 Job terminated.
(1) Normal termination (return value 0)
Usr 0 00:00:01, Sys 0 00:00:04 - Run Remote Usage
Usr 0 00:00:00, Sys 0 00:00:00 - Run Local Usage
Usr 0 00:00:01, Sys 0 00:00:04 - Total Remote Usage
Usr 0 00:00:00, Sys 0 00:00:00 - Total Local Usage
10428298 - Run Bytes Sent By Job
0 - Run Bytes Received By Job
10428298 - Total Bytes Sent By Job
0 - Total Bytes Received By Job
Thanks for your comments
[OFF-TOPIC]
--------------------
Jose are you in GridColombia's list?