Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] (no subject)
- Date: Wed, 13 Jun 2007 16:34:31 +0100
- From: "Kewley, J \(John\)" <j.kewley@xxxxxxxx>
- Subject: Re: [Condor-users] (no subject)
> Yes that is what was happening. The temp files were being deleted once
> the batch file was returned. I noticed that but was unsure what was
> happening but that makes sense.
Starting things in a new window wouldn't help either since condor
usually runs as low privilege and users would get annoyed if new windows
started popping up on their machine!
> I don't think I can because the executable was a program that was sent
> to me by a co-worked in order to test condor. Maybe it could have been
> though I am not too sure because I am very new with all of this. How
> would you have run it directly?
Your choices:
(other settings same as before unless otherwise stated)
==================== Running directly
executable = build_looks.exe
arguments = "-f long_run.props"
transfer_inputs = <as before but no needfor build_looks.exe now>
===
No need for build.bat
==================== Running using batch file
Same as before
=== build.bat is simply:
====
build_looks.exe -f long_run.props
==================== Using start
==================== (although I have no idea why you would want to do this)
Same as before except with /B, /WAIT or both.
====================
Note, if you have been doing this testing all on the same machine,
then I have a concern that using start is an extra complication that
you don't want when running on remote machines.
Cheers
JK
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of
> Richardson, Joshua
> Sent: Wednesday, June 13, 2007 4:10 PM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] (no subject)
>
>
>
> Josh Richardson
> Integrity Applications Incorporated Intern (IAI)
> 703-378-8672 ext 632
>
>
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Jones, Torrin A
> (US SSA)
> Sent: Wednesday, June 13, 2007 10:57 AM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] (no subject)
>
> start /? returns . . .
>
> . . .
>
> B Start application without creating a new window. The
> application has ^C handling ignored. Unless the
> application
> enables ^C processing, ^Break is the only way to
> interrupt
>
> . . .
>
> WAIT Start application and wait for it to terminate
> the application
>
> . . .
>
> As well as a lot of other output, but you only asked about the /B and
> /WAIT.
>
> I think the key may be the /WAIT for 2 reasons that I haven't tested.
>
> 1. When you run an executable in a batch file, the batch file doesn't
> wait for the executable to be completed.
>
> 2. When the batch file returns, i think condor deletes the temporary
> execute directory.
>
> Like I said I haven't tested this, it's just my theory.
>
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Richardson,
> Joshua
> Sent: Wednesday, June 13, 2007 07:55
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] (no subject)
>
>
> No I haven't but I am trying it right now. Thanks. Quick
> question...what
> does the /B/WAIT do?
>
> Josh Richardson
> Integrity Applications Incorporated Intern (IAI)
> 703-378-8672 ext 632
>
>
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Jones, Torrin A
> (US SSA)
> Sent: Wednesday, June 13, 2007 10:47 AM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] (no subject)
>
> Have you tried changing you batch file start command to . . .
>
> start /B /WAIT build_looks.exe -f long_run.props
>
>
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Richardson,
> Joshua
> Sent: Wednesday, June 13, 2007 07:33
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] (no subject)
>
>
> I have done that as well. I made sure it ran by hand before running it
> in condor. In the cmd I type in start build_looks.exe -f
> long_run.props.
> Maybe that is an incorrect way of calling in Condor. My
> build.bat is the
> same (start build_looks.exe -f long_run.props)
>
> Josh Richardson
> Integrity Applications Incorporated Intern (IAI)
> 703-378-8672 ext 632
>
>
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of
> Kewley, J (John)
> Sent: Wednesday, June 13, 2007 10:04 AM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] (no subject)
>
> > It runs fine outside of condor. If I double click on the batch file
> > build.bat the program opens and runs and closes after 2-3
> > minutes. When
> > it closes, looks.txt and looks_angles.txt are in the directory with
> > build.bat. I was told it only needs those two programs. This isn't a
> > program that I have made but someone made for testing Condor.
>
> Try and mirror what condor does, condor doesn't "click".
>
> 1. Go to the machine that was trying to run your code
> 2. create an empty directory and copy into it the same
> files as were in your condor directoy
> 3. then using the cmd shell, run the command by hand.
>
> This ensures that it works outside of condor on that machine.
>
> You could also try running condor_hold to freeze while it is
> running and then go to that machine and run it there by hand.
>
> Sorry if I am not being much help, but it is likely to be something
> simple and the person who gave you it may have forgotten about a file
> which
> is accessible (say through networked filestore) in the place where you
> run it, but not available to condor.
>
> Cheers
>
> JK
>
> _______________________________________________
> 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/
>
> _______________________________________________
> 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/
>