11-02-2009
Background job when completed
Hello - I submitted one background job last night and it completed today morning.I want to know exact time the job completed.
I submitted backgroung job like this
nohup cp -Rp /opt/apps/prod/proddb/proddata . &
I want to know when above job completed on UNIX server.Above command submitted on following server.
SunOS proddb 5.10 Generic_141414-09 sun4u sparc SUNW,Sun-Fire-880
Thanks in advance.
Mansoor.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I try to run a script as background job.
script:
#!/usr/bin/csh
/usr/bin/date +20%y-%m-%d > ~/datsql.txt
If I start it I got this output:
tac> ./datermitteln&
293
+ Stopped (SIGTTOU) ./datermitteln&
I insert the following line inside my script, but without any... (3 Replies)
Discussion started by: joerg
3 Replies
2. UNIX for Dummies Questions & Answers
Hiya,
Recently I've run a few scripts in the foreground, but have realised later they should of been better nohup'd and placed in the background. I understand how to change a foreground job into a background one, but how would put the job into the nohup state?
Thanks (1 Reply)
Discussion started by: rdbooth
1 Replies
3. UNIX for Dummies Questions & Answers
on gnome i open a terminal and run wget http://soommmething & in the background. because wget shows me downloading progress percentage and download speed continuously, I exit the gnome-terminal
after a while i want to see the download percentage but dont know how. my ps -u myname shows that... (3 Replies)
Discussion started by: babayeve
3 Replies
4. Solaris
Hi,
Thanks in advance.
i need to kill a unix background running job after that job process completes.
i can kill a job by giving the following unix command
kill -9 processid
how to kill the job after the current process run gets completed ?
Appreciate your valuable help.
Thanks... (7 Replies)
Discussion started by: dtazv
7 Replies
5. Shell Programming and Scripting
Hi Experts,
I need a script advice to schedule 12 jobs ( SAS Codes execute back ground ).
Algorithem:
1. Script checks first job.
2. Finds first job is done; invoke second job.
3. finds second job is done; invoke third job.
..
Request you to please assist. (3 Replies)
Discussion started by: Jerald Nathan
3 Replies
6. Shell Programming and Scripting
Hi,
The HPCs I used earlier used PBS (Portable Batch System) to schedule when I was running various jobs and it had an option to send me an email once a job is completed.
I'm wondering whether this is possible for any other process (without the use of PBS). For example, I'm running some codes... (2 Replies)
Discussion started by: lost.identity
2 Replies
7. Shell Programming and Scripting
Hello Everyody,
Having a doubt.
sort file1 &
when we sent a job to the background it returns
Job Number
PID
again if we want to ... (1 Reply)
Discussion started by: knroy10
1 Replies
8. Shell Programming and Scripting
I'm running diff at the command prompt against two very large text files (>1GB) and system kills the process and replys back "Terminated" after 15 seconds.
I believe a system parameter needs to be adjusted but can't figure it out.
I'm running Red Hat 4.1.2-46, 2.6.18-028stab089.1
Thanks... (4 Replies)
Discussion started by: azpetef
4 Replies
9. Shell Programming and Scripting
How to bring a backgroud job say sample_script.sh to foreground (4 Replies)
Discussion started by: rafa_fed2
4 Replies
10. Shell Programming and Scripting
HI All,
I need the answer of below question?
1) how to find the shellscript which is running In background is completed or not ?
ex: I know the shellscript name abc.sh which is running in background through cronjob. I want to know this is job is still running or stopped, how to... (3 Replies)
Discussion started by: pspriyanka
3 Replies
pbs(1B) PBS pbs(1B)
NAME
pbs - general information on pbs
DESCRIPTION
PBS stands for Portable Batch System. It is a networked subsystem for submitting, monitoring, and controlling a work load of batch jobs on
one or more systems. More information about PBS is available in the PBS Users Guide.
Batch means that the job will be scheduled for execution at a time chosen by the subsystem according to a defined policy and the availabil-
ity of resources. For a normal batch job, the standard output and standard error of the job will be returned to files available to the
user when the job is complete. This differs from an interactive session where commands are executed when entered via the terminal and
output is returned directly to the terminal. PBS also supports an interactive batch mode where the input and output is connected to the
user's terminal, but the scheduling of the job is still under control of the batch system.
A job is typically a shell script and a set of attributes which provide resource and control information about the job. A job does not
have to be submitted on the system where it will run, tt can be submitted on any system with the PBS commands and access to the execution
system, see qsub(1B). Output will be returned to the system from which the job was submitted unless directed otherwise.
Attributes offer control over when a job is eligible to be run, what happens to the output when it is completed and how the user is noti-
fied when it completes. The attributes of the job may be specified on the command line or in the job script when the job is submitted.
For information about job attributes, see qsub(1B) and pbs_job_attributes(7B).
One important attribute is the resource list. The list specifies the amount and type of resources needed by the job in order to execute.
The list also implies a hard upper limit on usage of those resources. When the limit is reached, the job is terminated. The types of
resources available to a job vary with the system architecture. For a list of resources supported on the default system, see
pbs_resources(7B). There are man pages for other systems types as well, see pbs_resources_aix4(7B), pbs_resources_fujitsu(7B),
pbs_resources_irix5(7B), pbs_resources_solaris5(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), or pbs_resources_unicos8(7B).
Once a job has been submitted, it may be monitored by use of the qstat(1B) command. Two forms of output are available with the qstat com-
mand. The default form is the short display. Information about a job is limited to a single line. Complete information about the job
or jobs is available through qstat with the -f option. Information will be given about all jobs in the system, all jobs in specified
queues, or only specified jobs.
When displaying status of jobs, you will see in which queue the job resides. In PBS a queue is just a collection point for jobs, it does
not imply any execution ordering. That ordering is determined by a scheduling policy implemented by the system administration.
Other commands of interest which have man pages of their own are:
qalter Alter a job's attributes.
qdel Delete a job.
qhold Place a hold on a job to keep it from being scheduled for running.
qmove Move a job to a different queue or server.
qmsg Append a message to the output of an executing job.
qrerun Terminate an executing job and return it to a queue.
qrls Remove a hold from a job.
qselect Obtain a list of jobs that met certain criteria.
qsig Send a signal to an executing job.
SEE ALSO
qalter(1B), qdel(1B), qhold(1B), qmove(1B), qmsg(1B), qrerun(1B), qrls(1B), qselect(1B), qsig(1B), qsub(1B) and the PBS User Guide. Start-
ing with qsub(1B), you can find all other available PBS man pages by following references in the "See Also" section.
Local pbs(1B)