Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] 'simple' c++ program
- Date: Mon, 21 Jan 2008 23:34:35 -0000
- From: "Kewley, J (John)" <j.kewley@xxxxxxxx>
- Subject: Re: [Condor-users] 'simple' c++ program
Executable gets transferred by default.
In this case, prog.bat is the executable so no need to Xfer.
If you make prog.exe the executable and do away with prog.bat,
then you can (should?) remove it from the transfer_input_files list.
Of course, if you do away with prog.bat, you lose the chance of extra
debug info telling you what is happening (or not as in this case)
Other thoughts:
* It is usual (recommended?) to have one per job cluster, not one per job.
you are only queuing one job so it shouldn't make much difference.
* Does the error file get its timestamp updated after running the job?
JK
-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx on behalf of Philip Crawford
Sent: Mon 21/01/2008 23:24
To: 'Condor-Users Mail List'
Subject: Re: [Condor-users] 'simple' c++ program
Stephen,
Do you need to run from the batch file?
Try just having
Executable=prog.exe
with the arguments as given.
i.e., the KISS principle.
But, then again, if running from the batch file, do you need to transfer the
file prog.bat also? I'm a bit rusty.
Cheers,
Phil
_____________________________________________
Philip Crawford B Comp Sc, MIEEE
Medicine Computer Support Unit
The University of NSW, Sydney, NSW, 2052
Phone: +61-2-9385 2564
Fax: +61-2-9385 1258
Email: p.crawford@xxxxxxxxxxx
_____________________________________________
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Stephen Upton
Sent: Tuesday, 22 January 2008 10:09 AM
To: Condor-Users Mail List
Subject: Re: [Condor-users] 'simple' c++ program
Hi All,
Nope, that didn't work. Compiled with Gnu C++ as a standalone executable.
Other ideas?
thanx
steve
On Jan 21, 2008, at 5:42 PM, Stephen Upton wrote:
Hi Alan,
No, I don't think it was complied with cygwin g++. I'll check into that. I
don't see an 'objdump' command either (under cygwin. ?)
thanx - you gave me someplace else to look, though
steve
On Jan 21, 2008, at 5:19 PM, Alan Cass wrote:
Hey Steve,
How was prog.exe compiled? If it was compiled with cygwin g++ it probably
calls the Cygwin DLL (you can check with
objdump -p prog.exe | grep "DLL Name"
to see all DLLs it uses). This DLL is probably not necessarily available on
the execute machine. A quick fix would be to just transfer the cygwin1.dll
(or any other unavailable, but required, DLLs) with the executable.
Alan
On 22/01/2008, Stephen Upton < scupton@xxxxxxx <mailto:scupton@xxxxxxx> >
wrote:
Hi all,
I'm trying to run a simple c++ program. I'm using version 6.8.1 (I
know - I need to upgrade!) on a windows xp cluster. However, I'm
submitting my job from a cygwin prompt. It appears to run since I get
output from my echo statements in the .bat file that I use to call
the c++ program. Here's the submit:
*****
Executable = prog.bat
requirements = OpSys == "WINNT50" || OpSys == "WINNT51"
getenv = true
Universe = vanilla
Error = Output/err.$(process)
Output = Output/out.$(process)
Log = Output/log.$(process)
Should_Transfer_files = YES
When_To_Transfer_Output = ON_EXIT
transfer_input_files = prog.exe, R2.txt, initialnodes.txt ,
nodearccosts.txt, nodepcm.txt, S10solutionfile.txt
Arguments = 44 20 33750 12825 R2.txt
Queue
***
and here's prog.bat
echo running prog.exe %1 %2 %3 %4 %5
prog %1 %2 %3 %4 %5
echo done
****
I suspect it has something to do with prog.exe but not sure where to
look. I don't have access to the source code, but have access to the
programmer. ;-)
I've seen various other emails that are similar, e.g., running
Fortran programs, and I think I've covered the bases, but still feel
I'm missing something easy.
thanx
steve upton
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/