10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
I have the requirement that ,i have to write a shell script that job has to wait for a 7 touch files created by another application for 4 hours, if i get all 7 touch files ,i have to send a mail that i jobs are completed, if if it is waiting for more than 4 hours i have to send a mail... (2 Replies)
Discussion started by: Pradeep Shetty
2 Replies
2. Shell Programming and Scripting
Hi All,
I have a question related to Shell scripting. In my shell script, I have following two commands in sequence:
sed 's/^/grep "^120" /g' $ORIGCHARGEDAMTLIST|sed "s;$;| cut -f$FIELD_NO1 -d '|' | awk '{ sum+=\$1} END {printf (\"%0.2f\\\n\", sum/100)}' >$TEMPFILE
mv $TEMPFILE $ORIGFILE... (3 Replies)
Discussion started by: angshuman
3 Replies
3. Shell Programming and Scripting
Let's say I start process A.sh, then start process B.sh. I call both of them in my C.sh
How can I make sure that B starts its execution only after A.sh finishes.
I have to do this in loop.Execution time of A.sh may vary everytime.
It is a parameterized script. (17 Replies)
Discussion started by: rafa_fed2
17 Replies
4. Shell Programming and Scripting
Hi,
Can anyone help me how to exit a shell script if a unix command inside does not return any value for 10 seconds?
The scenarios is like this.
I want to login to a application using shell script where the connection string is mentioned.but suppose this connection string is not... (10 Replies)
Discussion started by: arijitsaha
10 Replies
5. Shell Programming and Scripting
hi, everyone.
My want to execute the shell script below per 10 seconds
PID=`pgrep java`
if
then
/home/java/java
fi
crontab wouldn't help me.
some one can give me suggestions?thanks
---------- Post updated at 07:29 AM ---------- Previous update was at 07:26 AM ----------
... (6 Replies)
Discussion started by: AKB48
6 Replies
6. Shell Programming and Scripting
Hi,
I am facing a strange issue,
when i call a script from my while loop in background it doesnt go in background, despite the wait i put below the whil loop it goes forward even before the process put in background is completed.
cat abc.txt | while read -u4 line
do
#if line contains #... (2 Replies)
Discussion started by: mihirvora16
2 Replies
7. Shell Programming and Scripting
HI,
I have a strange problem. A shell script that runs fine on solaris. when i ported to linux, it started hanging.
here is the core of the script
CFG_FILE=tab25.cfg
sort -t "!" -k 2 ${CFG_FILE} | egrep -v "^#|^$" | while IFS="!" read a b c
do
#echo "jobs output"
#jobs
#echo "jobs... (13 Replies)
Discussion started by: aksaravanan
13 Replies
8. Shell Programming and Scripting
guys I need emergency help with below shell script assignment..am new to shell script
Write a Shell script to automatically check that a specified user is logged in to the
computer.
The program should allow the person running the script to specify the name of the
user to be checked, the... (2 Replies)
Discussion started by: gurmad
2 Replies
9. Shell Programming and Scripting
Did not use 'wait' yet.
How I understand by now the wait works only for child processes, started background.
Is there any other way to watch completion of any, not related process (at least, a process, owned by the same user?)
I need to start a background process, witch will be waiting... (2 Replies)
Discussion started by: alex_5161
2 Replies
10. Shell Programming and Scripting
Hi
I am creating 3 background processes in my shell script using &.
I have obtained the 3 PIDs of the background processes using $!.
I need to wait for these to complete and i need the exit status of each of these.
If i use :
wait $PID1
wait $PID2
wait $PID3
and get the exit status of... (1 Reply)
Discussion started by: Vinaya
1 Replies
wait(1) User Commands wait(1)
NAME
wait - await process completion
SYNOPSIS
/bin/sh
wait [pid]...
/bin/jsh /bin/ksh /usr/xpg4/bin/sh
wait [pid]...
wait [% jobid...]
/bin/csh
wait
ksh93
wait [job...]
DESCRIPTION
The shell itself executes wait, without creating a new process. If you get the error message cannot fork,too many processes, try using the
wait command to clean up your background processes. If this doesn't help, the system process table is probably full or you have too many
active foreground processes. There is a limit to the number of process IDs associated with your login, and to the number the system can
keep track of.
Not all the processes of a pipeline with three or more stages are children of the shell, and thus cannot be waited for.
/bin/sh, /bin/jsh
Wait for your background process whose process ID is pid and report its termination status. If pid is omitted, all your shell's currently
active background processes are waited for and the return code is 0. The wait utility accepts a job identifier, when Job Control is enabled
(jsh), and the argument, jobid, is preceded by a percent sign (%).
If pid is not an active process ID, the wait utility returns immediately and the return code is 0.
csh
Wait for your background processes.
ksh
When an asynchronous list is started by the shell, the process ID of the last command in each element of the asynchronous list becomes
known in the current shell execution environment.
If the wait utility is invoked with no operands, it waits until all process IDs known to the invoking shell have terminated and exit with
an exit status of 0.
If one or more pid or jobid operands are specified that represent known process IDs (or jobids), the wait utility waits until all of them
have terminated. If one or more pid or jobid operands are specified that represent unknown process IDs (or jobids), wait treats them as if
they were known process IDs (or jobids) that exited with exit status 127. The exit status returned by the wait utility is the exit status
of the process requested by the last pid or jobid operand.
The known process IDs are applicable only for invocations of wait in the current shell execution environment.
ksh93
wait with no operands, waits until all jobs known to the invoking shell have terminated. If one or more job operands are specified, wait
waits until all of them have completed. Each job can be specified as one of the following:
number number refers to a process ID.
-number number refers to a process group ID.
%number number refers to a job number
%string Refers to a job whose name begins with string
%?string Refers to a job whose name contains string
%+ Refers to the current job
%%
%- Refers to the previous job
If one ore more job operands is a process id or process group id not known by the current shell environment, wait treats each of them as if
it were a process that exited with status 127.
OPERANDS
The following operands are supported:
pid The unsigned decimal integer process ID of a command, for which the utility is to wait for the termination.
jobid A job control job ID that identifies a background process group to be waited for. The job control job ID notation is applicable
only for invocations of wait in the current shell execution environment, and only on systems supporting the job control option.
USAGE
On most implementations, wait is a shell built-in. If it is called in a subshell or separate utility execution environment, such as one of
the following,
(wait)
nohup wait ...
find . -exec wait ... ;
it returns immediately because there is no known process IDs to wait for in those environments.
EXAMPLES
Example 1 Using A Script To Identify The Termination Signal
Although the exact value used when a process is terminated by a signal is unspecified, if it is known that a signal terminated a process, a
script can still reliably figure out which signal is using kill, as shown by the following (/bin/ksh and /usr/xpg4/bin/sh):
sleep 1000&
pid=$!
kill -kill $pid
wait $pid
echo $pid was terminated by a SIG$(kill -l $(($?-128))) signal.
Example 2 Returning The Exit Status Of A Process
If the following sequence of commands is run in less than 31 seconds (/bin/ksh and /usr/xpg4/bin/sh):
sleep 257 | sleep 31 &
jobs -l %%
then either of the following commands returns the exit status of the second sleep in the pipeline:
wait <pid of sleep 31>
wait %%
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of wait: LANG, LC_ALL, LC_CTYPE, LC_MES-
SAGES, and NLSPATH.
EXIT STATUS
ksh93
The following exit values are returned by the wait built-in in ksh93:
0 wait was invoked with no operands. All processes known by the invoking process have terminated.
127 job is a process id or process group id that is unknown to the current shell environment.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
|Standard |See standards(5). |
+-----------------------------+-----------------------------+
SEE ALSO
csh(1), jobs(1), ksh(1), ksh93(1), sh(1), attributes(5), environ(5), standards(5)
SunOS 5.11 13 Mar 2008 wait(1)