09-11-2012
The definition doesn't seem to be clear. Why don't you try it out?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
i have a problem with turning a job into backgrund.
When i enter this at the shell:
spice -b darlington.cir -r output.raw > screenout.tmp &
and then let me show the currently running jobs, i get the following output:
+ Suspended (tty output) spice -b darlington.cir -r output.raw >... (4 Replies)
Discussion started by: qsi
4 Replies
2. Programming
Hi there,
I'm quite new to UNIX for programming. I have a script that does this:
Shows on screen real-time results taken from phone calls and logs them in a file.
However, when I start my script, I want my script to start logging in the file in the background, so I can continue working on... (1 Reply)
Discussion started by: Jeremiorama
1 Replies
3. Shell Programming and Scripting
i need to execute 5 jobs at a time in background and need to get the exit status of all the jobs i wrote small script below , i'm not sure this is right way to do it.any ideas please help.
$cat run_job.ksh
#!/usr/bin/ksh
####################################
typeset -u SCHEMA_NAME=$1
... (1 Reply)
Discussion started by: GrepMe
1 Replies
4. UNIX for Advanced & Expert Users
Reposting, as it got lost during the database backup. :(
Via a shell script a spawn 3 background jobs namely a, b & c.
These will take different times to complete.
I want to print a different message on completion of each.
How can i find out when each one has completed independently.
... (19 Replies)
Discussion started by: vibhor_agarwali
19 Replies
5. UNIX for Dummies Questions & Answers
If I run a job in the background and logoff. Will the job continue to run or will my processes be killed ? (1 Reply)
Discussion started by: jxh461
1 Replies
6. UNIX for Advanced & Expert Users
What is the difference between running a process using nohup and running a process in background ? Please explain (6 Replies)
Discussion started by: srksn
6 Replies
7. Solaris
Admins,
We have a strange problem on our solaris zones. We have four zones on a Global server (Sun-Fire-V890; Solaris 10 Update 6) and the SSH sessions to all four zones are terminated at a specific time (11:10 PM) every night. The SSH session to the global server is not terminated.
Also, any... (1 Reply)
Discussion started by: yogijp
1 Replies
8. Programming
Hello,
I am trying to find a way to send several sequential commands via SSH to a remote box in a single command.
Thoughts so far:
1) Can I put them into a function and call the function within the ssh command?
e.g.
ssh <targetserver> $(functionx)
No - then it calls the function in... (4 Replies)
Discussion started by: doonan_79
4 Replies
9. Shell Programming and Scripting
Please I have run a background script using nohup please tell me way to stop this. Thanks in Advance (4 Replies)
Discussion started by: mumakhij
4 Replies
10. UNIX for Dummies Questions & Answers
I have a question.
I will be running a background process using nohup and & command at end. I want to send output to a file say myprocess.out.
So will this command work?
nohup myprocess.ksh > myprocess.out &
Thanks in advance guys !!!
:) (3 Replies)
Discussion started by: vx04
3 Replies
LEARN ABOUT CENTOS
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)