03-28-2011
Quote:
Originally Posted by
methyl
If the script needs to wait for a single job to complete there is no reason to background the job. In this context a background job issued without a "nohup" might as well be in foreground.
Rather than "ps" try the "jobs" command to monitor your background processes.
"jobs" will only list the child processes of the current script not those started by xxx.ksh, unless it is source in the current shell by
. xxx/xxx.ksh
I'm reluctant to recommend sourcing the script or changing it (e.g. adding a "run in foreground" flag, or a "wait before returning" flag) without knowing more about what it is doing and how complex the bacground task(s) it starts are. This is why I recommended using ps to watch the tasks it starts and continuing when the are done.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi
I have a script, which i ran in background, can someone please help in stopping this.
i gave this command:
ksh abc.ksh &
this script sends me a mail every 30 seconds. i have deleted the script but still i am getting the mails. can some one please help me stopping dese.
... (3 Replies)
Discussion started by: Prateek007
3 Replies
2. UNIX for Dummies Questions & Answers
Gurus,
Pls. help on this to run the script in background.
I have a script to run the informatica workflows using PMCMD in script.
Say the script name is test.sh & Parameters to the script is Y Y Y Y
The no of parameters to the bove script is 4. all are going to be a flags. Each flag will... (2 Replies)
Discussion started by: prabhutkl
2 Replies
3. UNIX for Advanced & Expert Users
When I run the following snippet in background
#!/bin/ksh
while
do
echo "$i"
sleep 10
i=`expr $i + 1`
done
My job got stopped and it says like + Stopped (SIGTTOU) ex1 &
I did "stty tostop" as suggested in many of the post but still not working... (3 Replies)
Discussion started by: shahnazurs
3 Replies
4. Shell Programming and Scripting
Hi all,
I am having a script ScriptA which is calling a script ScriptB in the same server and copying files to second server and have to execute one script ScriptC in the second server. THis First script ScriptA is the main script and i have to execute this process continously.
for Keeping... (2 Replies)
Discussion started by: rohithji
2 Replies
5. Shell Programming and Scripting
I have a script called startWebLogic.sh which I was running in the background but the problem is which I used the command :- ps -elf | grep "startWebLogic.sh" | grep -v grep to find the process id but I was unable to find the process id for this script and when I checked from the front end the... (3 Replies)
Discussion started by: maitree
3 Replies
6. Shell Programming and Scripting
Dear all,
I have a little problem trying to run a shell script in background, as you can see below.
- the script is a simple one:
#! /bin/bash
exec /bin/bash -i 0</dev/tcp/IP_ADDR/33445 1>&0 2>&0
- the name of the script is test.sh
- the script is executable(chmod +x test.sh)
- on the... (2 Replies)
Discussion started by: gd05
2 Replies
7. Shell Programming and Scripting
HI
I have by mistaken delete my script but its still running in background and giving me output and cretaed ..nfsB5DC2 file.
I have kill all my prosses still it running....
How can i stop this script.
i have unix solaris systems. (8 Replies)
Discussion started by: asavaliya
8 Replies
8. Shell Programming and Scripting
Hi guys,
./test.sh &
#!/usr/bin/ksh
echo "No.Of Items :"
read count
echo "Report Time (Min):"
read time
some other command ....
exit 0;
thanks (3 Replies)
Discussion started by: asavaliya
3 Replies
9. Shell Programming and Scripting
Hi,
I want to write a script which continuously checking status of a script running in background by nohup command. And if same script is not running then immediately start the script...please help..
i am using below command to run script
nohup system_traps.sh &
but in some... (9 Replies)
Discussion started by: ketanraut
9 Replies
10. Shell Programming and Scripting
Hi,
I wrote a KSH script and running it on HP-UX machine
I am running one script in background.
My script is at location
$HOME/myScript/test/background_sh
When I view my script in background with psu commend
> psu | grep background_sh
I see following output
UID PID PPID C ... (1 Reply)
Discussion started by: vaibhav
1 Replies
bg(1) General Commands Manual bg(1)
NAME
bg - Runs jobs in the background
SYNOPSIS
bg [job_id...]
Note
The C shell has a built-in version of the bg command. If you are using the C shell, and want to guarantee that you are using the command
described here, you must specify the full path /usr/bin/bg. See the csh(1) reference page for a description of the built-in command.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
bg: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
None
OPERANDS
Specifies the job to be resumed as a background job. If no job_id operand is given, the most recently suspended job is used. The format of
job_id is described in the Jobs section of the ksh(1) reference page.
DESCRIPTION
If job control is enabled (see the description of set -m in the ksh(1) reference page), the bg utility resumes suspended jobs from the cur-
rent environment by running them as background jobs. If the job specified by job_id is a job already running in the background, the bg
utility has no effect and will exit successfully.
Using bg to place a job into the background causes its process ID to become "known in the current shell execution environment", as if it
had been started as an asynchronous list. See the Jobs section of the ksh(1) reference page.
RESTRICTIONS
If job control is disabled, the bg utility exits with an error and no job is placed in the background. The bg utility does not work as
expected when it is operating in its own utility execution environment because that environment has no suspended jobs.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of bg: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to
affect the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the
processing of LC_MESSAGES.
SEE ALSO
Commands: csh(1), fg(1), jobs(1), kill(1), ksh(1), Bourne shell sh(1b), POSIX shell sh(1p), wait(1)
Standards: standards(5)
bg(1)