I have an ftp user, which has been setup to run ftp jobs to a specific machine (different jobs). for the first job i created .netrc in the ftp users home directory and added the appropriate commands
machine FTPBOX01 login user1 password xxx
macdef init
etc
etc
get file
bye
I use the... (3 Replies)
Is there any way I can submit a job to a remote machine and return immediately without withing for the job to finish?
What I mean is this...using rsh I can submit a job to a remote machine like this:
rsh remotemac1 job.sh
But this doesn't return untill the job has finished and as a... (3 Replies)
I have a list of jobs. their expected start time and their expected duration.
my needs are
monitor multiple jobs (starting at different time and their execution time also differs)
Need to mail if any of the job running longer than its expected duration.
Whats the efficient way to scripting... (1 Reply)
Hello,
I would like to write a perl script which executes several jobs. The key thing is I only want 4 jobs to be executed at one time (that's because my machine as 4 cpu, and I want one job per cpu). Is there any way that I can get perl to co-operate with me in this?
Thanks! (1 Reply)
Hello,
I have a perl script that takes in one file of input and outputs to a file. I would like to run this script on several input files, and I would like to run it with qsub, something like this:
Input files:
FileListDssp.txt.numaa
FileListDssp.txt.numab
FileListDssp.txt.numac
etc..
... (1 Reply)
I have a sequence of tasks that I routinely run and I'm trying to parallelize certain portions of the sequence. Specifically, there are 3 tasks which all read from the same file, each performing different operations and writing to their own seperate file. I was wondering if I could execute these... (3 Replies)
Hi,
I ran two crontab commands
using:
crontab program1
crontab program2
However when I type crontab -l only the second cron job shows up, how do I see all cron jobs running and how do I edit all at the same time
Thanks in Advance
S:D (10 Replies)
Hi
I am new to submitting jobs. I am trying to submit my perl file to the cluster.
This is what my shell file looks like (shell1.sh):
#!/bin/sh
#$ -S /bin/sh
cd data/projects/mydir/abbc
perl autocorro.pl
followed by qsub shell1.sh
It takes the qsub, but does nothing. I check... (1 Reply)
I have multiple jobs and each job dependent on other job.
Each Job generates a log and If job completed successfully log file end's with JOB ENDED SUCCESSFULLY message and if it failed then it will end with JOB ENDED with FAILURE.
I need an help how to start.
Attaching the JOB dependency... (3 Replies)
I have two scripts which I'm tying to run one after the other- this is what I've tried:
00 14 * * * /path/one.sh && /path/two.sh
I've also tried putting each script on a different line:
00 14 * * * /path/one.sh
00 14 * * * /path/two.sh
Can this be done? (1 Reply)
Discussion started by: $shell_Learner
1 Replies
LEARN ABOUT DEBIAN
sge_request
SGE_REQUEST(5) Sun Grid Engine File Formats SGE_REQUEST(5)NAME
sge_request - Sun Grid Engine default request definition file format
DESCRIPTION
sge_request reflects the format of the files to define default request profiles. If available, default request files are read and processed
during job submission before any submit options embedded in the job script and before any options in the qsub(1) or qsh(1) command-line are
considered. Thus, the command-line and embedded script options may overwrite the settings in the default request files (see qsub(1) or
qsh(1) for details).
There is a cluster global, a user private and a working directory local default request definition file. The working directory local
default request file has the highest precedence and is followed by the user private and then the cluster global default request file.
Note, that the -clear option to qsub(1) or qsh(1) can be used to discard any previous settings at any time in a default request file, in
the embedded script flags or in a qsub(1) or qsh(1) command-line option.
The format of the default request definition files is:
o The default request files may contain an arbitrary number of lines. Blank lines and lines with a '#' sign in the first column are
skipped.
o Each line not to be skipped may contain any qsub(1) option as described in the Sun Grid Engine Reference Manual. More than one option
per line is allowed. The batch script file and argument options to the batch script are not considered as qsub(1) options and thus are
not allowed in a default request file.
EXAMPLES
The following is a simple example of a default request definition file:
=====================================================
# Default Requests File
# request group to be sun4 and a CPU-time of 5hr
-l arch=sun4,s_cpu=5:0:0
# don't restart the job in case of system crashes
-r n
=====================================================
Having defined a default request definition file like this and submitting a job as follows:
qsub test.sh
would have precisely the same effect as if the job was submitted with:
qsub -l arch=sun4,s_cpu=5:0:0 -r n test.sh
FILES
<sge_root>/<cell>/common/sge_request
global defaults file
$HOME/.sge_request user private defaults file
$cwd/.sge_request cwd directory defaults file
SEE ALSO sge_intro(1), qsh(1), qsub(1), Sun Grid Engine Installation and Administration Guide
COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions.
SGE 6.2u5 $Date$ SGE_REQUEST(5)