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,
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?
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)
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)
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)
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)
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)
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)
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)
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)
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
npm-run-script
NPM-RUN-SCRIPT(1)NPM-RUN-SCRIPT(1)NAME
npm-run-script - Run arbitrary package scripts
SYNOPSIS
npm run-script <command> [--silent] [-- <args>...]
alias: npm run
DESCRIPTION
This runs an arbitrary command from a package's "scripts" object. If no "command" is provided, it will list the available scripts.
run[-script] is used by the test, start, restart, and stop commands, but can be called directly, as well. When the scripts in the package
are printed out, they're separated into lifecycle (test, start, restart) and directly-run scripts.
As of ` https://blog.npmjs.org/post/98131109725/npm-2-0-0, you can use custom arguments when executing scripts. The special option -- is
used by getopt https://goo.gl/KxMmtG to delimit the end of the options. npm will pass all the arguments after the -- directly to your
script:
npm run test -- --grep="pattern"
The arguments will only be passed to the script specified after npm run and not to any pre or post script.
The env script is a special built-in command that can be used to list environment variables that will be available to the script at run-
time. If an "env" command is defined in your package, it will take precedence over the built-in.
In addition to the shell's pre-existing PATH, npm run adds node_modules/.bin to the PATH provided to scripts. Any binaries provided by
locally-installed dependencies can be used without the node_modules/.bin prefix. For example, if there is a devDependency on tap in your
package, you should write:
"scripts": {"test": "tap test/*.js"}
instead of
"scripts": {"test": "node_modules/.bin/tap test/*.js"}
to run your tests.
The actual shell your script is run within is platform dependent. By default, on Unix-like systems it is the /bin/sh command, on Windows it
is the cmd.exe. The actual shell referred to by /bin/sh also depends on the system. As of `
https://github.com/npm/npm/releases/tag/v5.1.0 you can customize the shell with the script-shell configuration.
Scripts are run from the root of the module, regardless of what your current working directory is when you call npm run. If you want your
script to use different behavior based on what subdirectory you're in, you can use the INIT_CWD environment variable, which holds the full
path you were in when you ran npm run.
npm run sets the NODE environment variable to the node executable with which npm is executed. Also, if the --scripts-prepend-node-path is
passed, the directory within which node resides is added to the PATH. If --scripts-prepend-node-path=auto is passed (which has been the
default in npm v3), this is only performed when that node executable is not found in the PATH.
If you try to run a script without having a node_modules directory and it fails, you will be given a warning to run npm install, just in
case you've forgotten.
You can use the --silent flag to prevent showing npm ERR! output on error.
You can use the --if-present flag to avoid exiting with a non-zero exit code when the script is undefined. This lets you run potentially
undefined scripts without breaking the execution chain.
SEE ALSO
o npm help 7 scripts
o npm help test
o npm help start
o npm help restart
o npm help stop
o npm help 7 config
January 2019 NPM-RUN-SCRIPT(1)