06-24-2009
I agree with "bwhited".
If possible, write the script to the lowest common denominator.
Failing that write a controlling script in basic shell which calls named scripts containing a shebang for the preferred shell.
I usually use "uname -s" to identify the environment, but a truly portable script will need to know versions.
IMHO variations on "echo", "find", "awk" (or "nawk"), and "df" (or "bdf") are the biggest pain. You either need a portable script which decides which command suits the environment or a suite of custom scripts for each environment.
BTW. If all your systems are modern this board will seek out the POSIX shell. No problem there.
Others may wish to comment.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I'm new to scripting and I need help with a bourn shell script. What i'm trying to do is a test condition where "if the time is within 2 hours, it's true" and so on.
The time is in the following format
DATE=`/bin/date +"%Y%m%d%H%S"`
for example, 20060907152000.
So, what the script first... (9 Replies)
Discussion started by: pieman8080
9 Replies
2. Windows & DOS: Issues & Discussions
Hello,
I am trying to accomplish the following.
Send the output of a command to the screen (this happens by default) as well as capture the output of the screen to a log file.
How can this be achieved in DOS command interpreter syntax.
Any ideas/suggesstions/indicators are greatly... (2 Replies)
Discussion started by: jerardfjay
2 Replies
3. UNIX for Dummies Questions & Answers
What is the difference between the(a) shell and the (a) command-line interpreter?
Here we're talking about the complete dummy question, but could someone point me right.
(yes, have written scripts in for instance bash shell,
and and grepp-ed my way around ....:eek: (4 Replies)
Discussion started by: amkgw
4 Replies
4. Shell Programming and Scripting
I am new to BASH and writing a small script to identify the SHELL .
#!/bin/bash
BASH='/bin/bash'
KSH='/bin/ksh'
if
then
echo "it's Bash"
else
echo "it's not Bash"
fi
$ bash -x a.sh
+ BASH=/bin/bash
+ KSH=/bin/ksh
+ ''
a.sh: line 4:
where am I missing . PLease advice . (10 Replies)
Discussion started by: talashil
10 Replies
5. Shell Programming and Scripting
I need clarification in -a test.
If say, in test -a left expression is not present but the right expression is present, do the shell will consider the left expression true and evaluate the right expression?
For example:
if ]
then
rm -f ${file}
fi
Is this test condition... (7 Replies)
Discussion started by: jatanig
7 Replies
6. Shell Programming and Scripting
I want to test connectivity between different servers with my server using information as IP and port only.
I have Name,IP List and port in one file. Please help how i can test connectivity is successful or not?
File format will be:
Name1,127.0.0.1,80
Name2,127.0.0.2,8080
Output could be ... (1 Reply)
Discussion started by: poweroflinux
1 Replies
7. UNIX for Dummies Questions & Answers
I am looking for a simple BASIC Interpreter written in a shell scripting language.
For me something like this would be a great learning tool...
After much goggle eyed Googling I came upon this:-
https://gist.github.com/cander/2785819
It is small and I haven't tried it yet as I am at work... (6 Replies)
Discussion started by: wisecracker
6 Replies
8. Shell Programming and Scripting
Dears ,
kindly I wanna do test for one KSH script to know how is it working , the problem that I'm facing is whenever put "sh -x ./my_script.sh"
the output seems very long & although I tried to to redirect it to files as it shown , but it failed :eek: :-
sh -x ./my_script.sh >... (2 Replies)
Discussion started by: arm
2 Replies
9. Solaris
Hello. We have recently changed from HP Unix Servers to Solaris. On the HP Severs we were using the POSIX shell. Solaris is using the Bourne sh.
We are using ksh as our default shell after login. The problem we are encountering is when something like Perl or Cron uses the shell to execute a... (5 Replies)
Discussion started by: mix123
5 Replies
10. Shell Programming and Scripting
Hi all and apologies for the silly question, but I've searched and I can't get this right.
I have a list of email addresses in a file that I need to blacklist (spam). the list is quite long and I would need to script a small routine so that I can get the following for each line in the file:
db... (4 Replies)
Discussion started by: bm555
4 Replies
LEARN ABOUT LINUX
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)