Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Shell script runs fine in Solaris, in Linux hangs at wait command
Top Forums Shell Programming and Scripting Shell script runs fine in Solaris, in Linux hangs at wait command Post 302467165 by aksaravanan on Thursday 28th of October 2010 11:34:57 AM
Old 10-28-2010
my apologizes for not using tag . and thanks for tagging.

1.
in both machines, i use ksh my program starts #!/bin/ksh , so it should override any shell is being used.

2. to answer the scenario , Robin's guess is right.
here is what i am doing

Code:
 
 
while read table, server_list
do
 
for server in server_list
do
do_somthing with table and server & # in background
done
wait # wait for all my background jobs to finish. 
echo now i can go and read next line 
 
done

now in my cash, wait started waiting for a zombie (unknown command, evetually a grep , sort) and never come out to read next line.

when i was trying to simplify the problem, i removed inner for loop , so my question looks awkward(stupid?)
technically, when i have while loop and have a wait command it shouldn't wait. ofcourse linux does something in background for while loops

i even used a intermediate file for doing sort and grep output and pass it on to while loop, but wait continue to hang.


again, when i started my config file with few lines, it was working fine in linux too. when i started adding more and more lines, it gave error

at one point, when i reduced row length from 260 char to 250 char , it worked too. but script still can work with line length exceeding more than 250 char when fewer lines were there. so i can't say this is the only scenario problem is exhibited.


could somebody help me to understand this..

thanks
AK
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Script runs fine on UNIX Server...Not through MSK Tool kit on Windows Server

I have a .sh script which was running fine on all the UNIX Servers (AIX, SunSolaris). The script requires two mandatory parameters and many optional parameters. Now at a different client place who are on a Windows Server, when I try to execute the script through MKS Toolkit, there are couple of... (5 Replies)
Discussion started by: madhunk
5 Replies

2. Shell Programming and Scripting

Script runs fine, but not in a cron

Okay, I have the following script that runs fine from a command line as well as an executable .sh file. It just moves any file/folder with movie* in the name to a folder called _Movies. The issue I'm running into is when it's call from a cron. find /mnt/HD_a2/BT/complete -iname "movie.*" -exec... (4 Replies)
Discussion started by: sammyk
4 Replies

3. Shell Programming and Scripting

Script Runs fine but not giving any output

Hi, My script is running with no erros but not giving any output can anyonehelp. #!/bin/ksh . /home/application/bin/application.env OUTFILE=Result.txt PROD_PASSWORD=`${GET_PWD} -f ${PWD_FILE_PATH} -s ${PROD_SERVER} -u ${PROD_USER}` echo "1)To get the book last loaded details " read... (7 Replies)
Discussion started by: jagadish_gaddam
7 Replies

4. Shell Programming and Scripting

awk command in script gives error while same awk command at prompt runs fine: Why?

Hello all, Here is what my bash script does: sums number columns, saves the tot in new column, outputs if tot >= threshold val: > cat getnon0file.sh #!/bin/bash this="getnon0file.sh" USAGE=$this" InFile="xyz.38" Min="0.05" # awk '{sum=0; for(n=2; n<=NF; n++){sum+=$n};... (4 Replies)
Discussion started by: catalys
4 Replies

5. Shell Programming and Scripting

CRON shell script only runs correctly on command line

Hi, I'm new to these forums, and I'm hoping that someone can solve this problem... To make things short: I have DD-wrt set up on a router. I'm trying to run a script in CRON that fetches the daily password from my database using SSH. CRON is set like so(in web interface): * * * *... (4 Replies)
Discussion started by: louieaw
4 Replies

6. Shell Programming and Scripting

Script runs fine manually but not in crontab

Hello Guys, I have scratched my head alot on this but couldn't find clue what's wrong. Can you please help me with this? My problem is as following. 1) When I manually execute following script it runs successfully with below output. bash-3.00# more smssend #!/bin/bash echo -e "<Request... (16 Replies)
Discussion started by: umarsatti
16 Replies

7. Shell Programming and Scripting

Part of the Shell script is not running via crontab, runs fine manually

Hello Team, As a part of my job we have made a script to automate a service to restart frequently. Script having two functions when executing it's should find the existing service and kill it, then start the same service . Verified the script it's working fine when executing... (18 Replies)
Discussion started by: gowthamakanthan
18 Replies

8. Shell Programming and Scripting

Script runs in command-line fine but times out in CRON?

Hi, I have a script that seems to run to completion when in the command-line, but when it is run using the cron, it seems to time out. They both start and run fine, but on the CRON it stops prematurely. The script hits an API every few seconds and grabs data. Does anyone have any idea on... (4 Replies)
Discussion started by: phpchick
4 Replies

9. Shell Programming and Scripting

In Shell Script Does Second Command Wait For First Command To Complete

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

10. Shell Programming and Scripting

Sql command inside shell script runs without giving anything back as outout

#!/bin/sh # This script returns the number of rows updated from a function echo "The execution is starting ....." sqlplus -silent $UP <<EOF set serveroutput on set echo off set pagesize 0 VAR no_rows_updated NUMBER; EXEC :no_rows_updated :=0; DECLARE CURSOR c_update is SELECT * FROM... (4 Replies)
Discussion started by: LoneRanger
4 Replies

LEARN ABOUT HPUX

queuedefs

queuedefs(4)						     Kernel Interfaces Manual						      queuedefs(4)

NAME

       queuedefs - queue description file for at, batch, and crontab

SYNOPSIS

DESCRIPTION

       The  file  describes  the characteristics of the queues managed by (see cron(1M)).  Each non-comment line in this file describes one queue.
       The format of the lines are as follows:

	      [njob[nice[nwait

       The fields in this line are:

	      q 	The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for  jobs  started	by
			(see  at(1)),  and  is	the  queue  for jobs run from a file (see crontab(1)).	Queue names through designate user-defined
			queues.

	      njob	The maximum number of jobs that can be run simultaneously in that queue.  Although any number can be specified here,  (see
			cron(1M))  by  default limits the number of jobs that can be run on all the queues to 100.  This limitation can be removed
			by setting the variable to 1 in the file.

	      nice	The value to give to all jobs in that queue that are not run with a user ID of	super-user  (see  nice(1)).   The  default
			value is 2.

	      nwait	The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that
			job's queue, or because more than 100 jobs were running in all the queues (see njob above).

EXAMPLES

       Consider the following file:

       The file is interpreted as follows:

	      The	     queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of
			     1.

			     Since  no	nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds
			     before trying again to run it (see cron(1M)).

	      The	     queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously.  Those jobs will be run with a value of 2.
			     If a job cannot be run because too many other jobs are running, will wait 90 seconds before trying again to run it.

       All  other  queues  can have up to 100 jobs running simultaneously.  They will be run with a value of 2, and if a job cannot be run because
       too many other jobs are running, will wait 60 seconds before trying again to run it.

SEE ALSO

       at(1), nice(1), crontab(1), cron(1M), proto(4).

STANDARDS CONFORMANCE

																      queuedefs(4)
All times are GMT -4. The time now is 10:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy