09-07-2015
Quote:
Originally Posted by
RudiC
To make scripts executable, you need to set its directory entry's "executable permissions" for the intended users/persons, "owner", "group", or "others". Enter chmod (all lower case) into the shell for this. Consider well which target users should receive that permission; in above sample you give it to all three groups.
nano is one among other editors used to modify scripts. It has nothing to do with the execution of a script.
The so called "shebang" within the script text is not mandatory but helps the shell decide which program to use to run the script.
I wanted to use nano as the editor, would I just write chmod in the editor and do it like that?
Thanks
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I've got a file named jdictd.sh containing the following:
--- begin file contents ---
#! /bin/csh
echo I\'m running!
java -cp jdictd.jar org.dict.server.JDictd data/dict.ini
# Use the following line instead if JRE 1.1 is used
# jre -cp jdictd.jar org.dict.server.JDictd data/dict.ini
---end... (2 Replies)
Discussion started by: ropers
2 Replies
2. AIX
Hi All:
I am a newbie.
I have shell script and bunch of java jar files and I want to give one single executable file (may be .bin).
Ex: I have test.sh, jar1.jar, jar2.jar. I have to make process.xxx
When we run "process.xxx" it will run the "test.sh" script which inturn uses jar1.jar and... (0 Replies)
Discussion started by: laxman123
0 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I am very new to UNIX and I have been learning about writing scripts and making them executable. I created a script called myscript. It has three lines:
#! /bin/sh
# This is my first shell script
echo friendsjustfriends
Now I try to run it using the sh command and it works
Next I... (4 Replies)
Discussion started by: rohitx
4 Replies
4. UNIX for Dummies Questions & Answers
making a script in vi to create a shell script called wherearethey by entering the following script:
echo -n "Who are you looking for: "read userif then list=`w | grep $user | cut -c19-30` if then echo "The user $user is logged in from $list" else echo "The user $user is not logged in... (3 Replies)
Discussion started by: curtner
3 Replies
5. Shell Programming and Scripting
Guys I placed
#!path/awk -f
placed awk script
and used $1 to call 1st inputfile inside the script.
But some where I did mistake. Could you please help me run this script as executable
I forgot to mention I also used BEGIN before placing awk script. But nothing worked out.
Script
... (2 Replies)
Discussion started by: repinementer
2 Replies
6. UNIX for Dummies Questions & Answers
Hi guys, i'm trying to make a file called 'run-all-tests' executable but it is not letting me for some reason. I am presented with the following error: chmod: cannot access `./run-tests': No such file or directory
Basically i have a folder called ex3 and within that there are task folders:... (11 Replies)
Discussion started by: Shyamz1
11 Replies
7. Shell Programming and Scripting
Hello,
I have a perl program called snp_hwe.pl
I have another program called hwe_test.run which contains the following:
for file in *.inp
do
cp $file genotype_counts_c.txt
./snp_hwe.exe > $file'.res'
done
I want to change my perl program to an executable program while changing... (3 Replies)
Discussion started by: Homa
3 Replies
8. UNIX for Advanced & Expert Users
I should make an executable on our server, and are having some problem (I changed this question cause I found out that anser).
I'm getting this error when trying to do make:
In file included from...
/usr/include/sys/file.h:161: error: expected specifier-qualifier-list before 'u_int'
*** Error... (1 Reply)
Discussion started by: 244an
1 Replies
9. Shell Programming and Scripting
Does it possible to make some bash script automatic to be a executable when transfered to another pc...? (5 Replies)
Discussion started by: tomislav91
5 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)