calling a shell script in background and wait using "wait" in while loop
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.
file contents for abc.txt ---------- Post updated at 06:23 PM ---------- Previous update was at 06:14 PM ----------
Any help will be appreciated.. Guys any pointers to what can be issue?
Hello All,
I am a newbie in Shell script programming, and maybe you can help me with my query.
I need to write a shell script (mntServer.ksh) that will start a background process and also to be able to run another script.
The mntServer.ksh script contains:
#!/bin/ksh... (1 Reply)
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)
can a wait command be run in background? or the script which has the wait command, be run background?
test.sh
-------
nohup a.sh &
nohup b.sh &
wait
nohup test.sh &
How can i run either wait or test.sh in background? i want test.sh to wait till a.sh and b.sh complete, and must be... (1 Reply)
Hi
I am writing a bash script on Solaris, that should take n arguments, either appended to the script or taken as output from the last command (similar to grep). What I don't want is that the script waits for user input. In other words:
Possibility 1:
script.sh arg1 arg2 arg3 ...Possibility... (4 Replies)
Hi,
I was wondering if pipes ("|"), or rather the command that follow them, know when they're supposed to wait for all the data?
For instance, if you take this:
cat my_file | sort | uniq
for uniq to work well, it needs to have rows sorted, but for lines to be sorted properly, it needs... (5 Replies)
Hello,
On a HP-UX 10.20 server I've executed something similar to this command:
# echo 'selall;info;wait;infolog;view;done' | /usr/sbin/cstm
But it returns sometype of "argument list too long" error.
I suppose there is a way to fix it by using xargs but I can't figure it out.
Any... (7 Replies)
Friends,
Need someone's help in helping me with the below requirement for a script:
> For a list of servers(over 100+), I need to login into each of them(cannot configure password-less ssh) & grab few configuration details <
I know, this is possible through expect programming in a simple... (2 Replies)
Friends,
Need someone's help in helping me with the below requirement for a script:
> For a list of servers(over 100+), I need to login into each of them(cannot configure password-less ssh) & grab few configuration details <
I know, this is possible through expect programming in a simple... (14 Replies)
Hi everyone,
I have a problem but I have never installed a separate OS before so my lingo and understanding may not be as good as some of you. I will try and explain my problem best I can. I am trying to instead of loading Windows 7 when my computer starts up, for it to start linux specifically... (2 Replies)
Discussion started by: markhow30
2 Replies
LEARN ABOUT NETBSD
wait
WAIT(1) BSD General Commands Manual WAIT(1)NAME
wait -- await process completion
SYNOPSIS
wait [pid]
DESCRIPTION
If invoked with no arguments, the wait utility waits until all existing child processes in the background have terminated.
Available operands:
pid If a pid operand is specified, and it is the process ID of a background child process that still exists, the wait utility waits until
that process has completed and consumes its status information, without consuming the status information of any other process.
If a pid operand is specified that is not the process ID of a child background process that still exists, wait exits without waiting
for any processes to complete.
The wait utility exits with one of the following values:
0 The wait utility was invoked with no operands and all of the existing background child processes have terminated, or the process
specified by the pid operand exited normally with 0 as its exit status.
>0 The specified process did not exist and its exit status information was not available, or the specified process existed or its exit
status information was available, and it terminated with a non-zero exit status.
If the specified process terminated abnormally due to the receipt of a signal, the exit status information of wait contains that termination
status as well.
STANDARDS
The wait command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
BSD June 5, 1993 BSD