Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: How will these subshell commands behave?
Top Forums Shell Programming and Scripting How will these subshell commands behave? Post 302883521 by LMHmedchem on Tuesday 14th of January 2014 06:03:01 PM
Old 01-14-2014
These scripts don't need to run in any particular order, there output is to files and each script is independent. They just need a bit of time in between when they start, and they both need to finish before the script moves on. The issue is that these two scripts (hex1, hex2) fire off six instances of an application and each instance reports some start up data back to the terminal. Because of the way that they are started, all of that start up data is mixed up and garbled. I am trying to debug a bit and can't read printout to the terminal that I need to look at.

Each script starts three instances of the app and there is a bit of sleep time between each, so if I run just one script, that output is clear. It is only when I run both scripts at the same time that I get this mess. I could not run the second script in the background and wait a bit before starting it, but I need to make sure that both scripts finish before moving on.

If I do what I posted,
Code:
   cd B/
   ./EV_B_m0-m200_hex1.sh &
   sleep 30
   ./EV_B_m0-m200_hex2.sh &
   wait

is this legal syntax? Will this start up hex1, wait for 30, start hex2, and then wait for both hex1 and hex2 to finish before moving on?

LMHmedchem
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Subshell Question

The profile of the user is empty. Then before I run the script I want I run a parameter file that populates the variables for oracle. ORACLE_HOME ORACLE_BASE ORACLE_SID PATH etc ... But it seems that these variables are not making it to the shell I am in because when I do an echo on... (6 Replies)
Discussion started by: lesstjm
6 Replies

2. UNIX for Dummies Questions & Answers

how to make ssh to behave as rsh

hi frnds, how to make the ssh service to behave as rsh.as we know ssh asks for passwd whereas the rsh doesnt.so how can i perform the followin operation without being asked for passwd. lets say i want to run the command "ls" on "remote_terminal" $ssh remote_terminal ls the above should work... (1 Reply)
Discussion started by: mxms755
1 Replies

3. Shell Programming and Scripting

Why does IF loop behave differently in different shells

Hi , I have a script that compares two string and prints the larger string , This is an extract of a biggers script that i have. #! /bin/ksh DT_STRING_CMP=20081221223440 DT_STRING=20071221223440 if ; then echo "20081221223440" fi echo... (1 Reply)
Discussion started by: amit1_x
1 Replies

4. Shell Programming and Scripting

Why does IF loop behave differently in different shells

Hi , I have a script that compares two string and prints the larger string , This is an extract of a biggers script that i have. #! /bin/ksh DT_STRING_CMP=20081221223440 DT_STRING=20071221223440 if ; then echo "20081221223440" fi echo... (5 Replies)
Discussion started by: amit1_x
5 Replies

5. Shell Programming and Scripting

mail command behave odd

hi, The following mail cmd executed successfully. mailx -s 'subject' user@company.com < testfile.dat However When i include this mail cmd in shell script it behave odd. Getting an error message mailx comand not found. (2 Replies)
Discussion started by: zooby
2 Replies

6. Shell Programming and Scripting

Killing a subshell

I am calling a script from with another script and reading its output one line at a time (using <childscript> | while read line) in the parent script. If the output exceeds a predefined number of lines I want to kill the child shell from within the parent shell. I decided to print the process ID... (2 Replies)
Discussion started by: slash_blog
2 Replies

7. Shell Programming and Scripting

getopts in a subshell

Hello, I've a little problem with one of my ksh scripts and I manage to narrow it to the script here: #!/bin/ksh writeLog() { paramHandle="unknown" OPTIND=1 while getopts :i: option $* do case $option in i) paramHandle=${OPTARG} ;; esac done echo... (2 Replies)
Discussion started by: Dahu
2 Replies

8. Shell Programming and Scripting

Basename in subshell

Hi All, I would like to improve my bash scripting skill and found a problem which I do not understand. Task is to search and print files in directory (and subdirecories) which contains its own name. Files can have spaces in name. This one works fine for files in main directory, but not for... (4 Replies)
Discussion started by: new_item
4 Replies

9. UNIX for Advanced & Expert Users

Why do awk command line vars behave the way they do?

This came up a little in another thread. Can someone explain some why awk (I happen to use gawk) behaves as follows: $ cat file aaa $ awk 'BEGIN {print x}' x=1 $ awk x=1 'BEGIN {print x}' awk: fatal: cannot open file `BEGIN {print x}' for reading (No such file or directory) $ awk -v... (6 Replies)
Discussion started by: hanson44
6 Replies

LEARN ABOUT NETBSD

dh_systemd_start

DH_SYSTEMD_START(1)						     Debhelper						       DH_SYSTEMD_START(1)

NAME

       dh_systemd_start - start/stop/restart systemd unit files

SYNOPSIS

       dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]

DESCRIPTION

       dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
       sysv init script is available.

       As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
       which case it will only be restarted after the upgrade).  This logic is not used when there is a corresponding SysV init script because
       invoke-rc.d performs the stop/start/restart in that case.

OPTIONS

       --restart-after-upgrade
	   Do not stop the unit file until after the package upgrade has been completed.  This is the default behaviour in compat 10.

	   In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.

	   This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
	   will not get confused by the package being upgraded while it's running before using this option.

       --no-restart-after-upgrade
	   Undo a previous --restart-after-upgrade (or the default of compat 10).  If no other options are given, this will cause the service to
	   be stopped in the prerm script and started again in the postinst script.

       -r, --no-stop-on-upgrade, --no-restart-on-upgrade
	   Do not stop service on upgrade.

       --no-start
	   Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
	   corresponding init script).

NOTES

       Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
       Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.

       Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
       in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.

SEE ALSO

       debhelper(7)

AUTHORS

       pkg-systemd-maintainers@lists.alioth.debian.org

11.1.6ubuntu2							    2018-05-10						       DH_SYSTEMD_START(1)
All times are GMT -4. The time now is 02:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy