[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] Windows - Condor 8.4.1 - queue command in submit file

I've tried all these suggestions but it seems to not even get to that stage.

It seems to be an error parsing the queue statement:

condor_submit -dry-run - test.sub
Dry-Run job(s)
ERROR: on Line 23 of submit file: not a valid command

ERROR: Failed to parse command file (line 23).

Same parse error without the dry-run option.

when using the statement:

queue fname from files.sh |

Works OK for windows but linux has this parsing problem.



-----Original Message-----
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Rich Pieri
Sent: Friday, 20 November 2015 10:55 PM
To: htcondor-users@xxxxxxxxxxx
Subject: Re: [HTCondor-users] Windows - Condor 8.4.1 - queue command in submit file

On 11/20/15 1:04 AM, Greg.Hitchen@xxxxxxxx wrote:
> #!/bin/bash
> ls -1 *.dat

Some advice:

Use /bin/sh rather than /bin/bash. /bin/sh will always exist on every
UNIX and UNIX-like system you come across. GNU BASH isn't universal and
it isn't always found as /bin/bash.

Always be explicit about paths to binaries whenever possible. A common
problem is that several shells' built-in echo don't work the same way as
/bin/echo with regards to certain switches such as -n. Use explicit
paths like /bin/ls to avoid inconsistent behavior problems down the line.

A less well known option is to add "-x" to your shebang:

 /bin/sh -x

This enables trace mode so you can see what the script is doing and
where it fails, and hopefully identify why.

Rich Pieri <ratinox@xxxxxxx>
MIT Laboratory for Nuclear Science
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: