I ran a program like following
Later I realized that this job will take more hours to complete. Since it consumed 2 hours dat aprocessing and I don't want to terminate and then start the job like
nohup sample.sh &
Can you please tell me, is it possible to make this job no hangup with out terminating it ?
Shahnaz.
Last edited by Yogesh Sawant; 05-24-2010 at 02:05 AM..
Reason: added code tags
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.
... (1 Reply)
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)
Hello,
I have bunch of shell scripts, which I want to execute every hour in the background. So I created a script mainscript.sh which executes these hourly scripts in the background. Script goes like this.
mainscript.sh
#!/bin/sh
nohup sh subscript1.sh &
nohup sh subscrip2.sh &
exit 0
... (5 Replies)
Yesterday I started a nohup job called assoc.sh. It has not finished running, but I have realised a problem with my script, so wish to cancel it, modify and restart it. However, I cannot find the PID, so can't cancel it. I have searched the ps list and nothing resembles my job - how can I cancel... (13 Replies)
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)
My job is launched using this command: I'm at home and having VPN drops so I used nohup and background.
nohup perf_mon -c rating_4_multi,cfg &
The main script is PID 26119, and the sub task under it is 26118 which is not running - just sits there. 26119 runs forever but nothing else runs. I... (2 Replies)
We need to configure autosys that when a job fails continously for 3 times, we need to call another job.
Is this possible in Autosys, or can anyone advice on the alternative. (2 Replies)
Shell : bash
OS : Oracle Linux 6.4
I want to save the ouput of a nohup command to file other than nohup.out . Below are my 3 attempts.
For both Attempt1 and Attempt2 , the redirection logs the output correctly to the output file. But I get the error "ignoring input and redirecting stderr to... (7 Replies)
Discussion started by: kraljic
7 Replies
LEARN ABOUT HPUX
proto
proto(4) Kernel Interfaces Manual proto(4)NAME
proto - prototype job file for at
SYNOPSIS DESCRIPTION
When a job is submitted to or the job is constructed as a POSIX shell script (see at(1)). The job file is created in as follows:
o creates a header describing the job as an job or a job. jobs submitted to all queues other than queue are listed as jobs. The header
is:
for an job, or
for a job.
o A set of POSIX shell commands is added to make the environment (see environ(5)) for the job the same as the current environment.
o then copies text from the prototype file to the job file, except for special variables that are replaced by other text:
Replaced by the current working directory.
Replaced by the current file size limit (see
ulimit(2)).
Replaced by the current umask (see
umask(2)).
Replaced by the time at which the job should be run,
expressed as seconds since January 1, 1970, 00:00 Coordinated Universal Time, preceded by a colon.
Replaced by text read by
from the standard input (that is, the commands provided to to be run in the job).
o When a job is submitted to queue queue, uses the file as the prototype file if it exists. Otherwise, it uses the file
EXAMPLES
The following file creates commands to change the current directory, file size limit, and umask in the job to their respective values as
they existed when was originally run. These commands are inserted before the commands in the job:
SEE ALSO at(1), queuedefs(4).
STANDARDS CONFORMANCE proto(4)