06-02-2009
From what you describe it looks like you have a race condition.
However without showing us the two scripts there is not much anybody can do to really help you figure out what is going on.
One suggestion, both your sleeps are set to 10 seconds. Change the first to 11 seconds and the second to 7 seconds.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi folks.
I'm just starting to teach myself shell scripting and am having some trouble with an if statement. I am working with a directory where only one file will reside at a time and need to evaluate if this file is compressed to determine subsequent steps. I'm using echo for testing purposes.... (2 Replies)
Discussion started by: kristy
2 Replies
2. Shell Programming and Scripting
Hi,
I found this strange behaviour while using one of the makefiles.
Here is the snippet of the unix.mak that is necessary for this context
SO = SvSocket.o SvStmt.o SvOdbcWrapper.o \
OdbcCallReader.o MgrCalls.o OdbcSvProxy.o \
OdbcSvApp.o... (4 Replies)
Discussion started by: vino
4 Replies
3. UNIX for Dummies Questions & Answers
I have a script which will look for a test folder under the parent directory. If the folder contains test folder then create the same directory structure in other remote machine.
Once the directories are created then transfer all the contents of that test folder.
this is what i am doing :-
... (2 Replies)
Discussion started by: chris1234
2 Replies
4. UNIX for Dummies Questions & Answers
Hello,
I am running into a bit of an issue running a Makefile. The problem is it was written for a xlf90 compiler when I have a pgf90 on the machine. Therefore, I keep getting errors regarding the xlf90 flags because they don't correspond with the pgf90. Here is the code:
... (0 Replies)
Discussion started by: lepagano
0 Replies
5. UNIX for Dummies Questions & Answers
Can anybody actually tell, what is flag? I know they are termed as permission flags and various others.
Please explain (3 Replies)
Discussion started by: nixhead
3 Replies
6. UNIX for Advanced & Expert Users
How to identify the scripts ran at a particular day of last month?
I have to identify a script that ran on 06/01/2011 @ 4 am (3 Replies)
Discussion started by: rdhanek
3 Replies
7. UNIX for Dummies Questions & Answers
Hi there,
I need your help in understanding the below Solaris 10 ifconfig output;
athnetspns02>ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0:... (2 Replies)
Discussion started by: wthomas
2 Replies
8. Shell Programming and Scripting
hello all,
i have the below script that we used to backup our DB using oracle's utility called RMAN. This has been working fine, but the issue is when the backup fails and we re-start it, it backups the whole thing again. Example.
lets say i have 5 database on my system(db1,db2,db3,db4,db5)... (11 Replies)
Discussion started by: crazy_max
11 Replies
9. Shell Programming and Scripting
tr a-z A-Z << END_TEXT
one two three
four five six
END_TEXT
i dont want this to be executed when someone runs the script that this is in. but for some reason, it gets executed. anywhere i can wrap this up in something to make sure it never gets executed?
another example:
cat <<... (1 Reply)
Discussion started by: SkySmart
1 Replies
10. UNIX for Advanced & Expert Users
Hi,
Please let me know if you have any thoughts on how to read a table that has all the oracle sql files or shell scripts at the job and step level to identify all the tables that does merge, update, delete, insert, create, truncate, alter table (ALTER TABLE XYZ RENAME TO ABC) and call them out... (1 Reply)
Discussion started by: techmoris
1 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)