Question on tweaking the PATH variable to allow the world to run my executable script
All,
I am pretty new to Unix and still in the learning curve I have a simple requirement for which I did not get an answer yet (Atleast I do not know how to keyword the search for my requirement!!!).
I have an executable script
Code:
my.script1
in a folder
Code:
/data/misc/scripts/dev
, which when executed calls 4 other background scripts
all running in background and also in the same folder (/data/misc/scripts/dev). The background scripts never come into picture from an User standpoint.
Now my requirement is I want to give my script (my.script1) to all the users and I dont want them executing the script by giving
Code:
/data/misc/scripts/dev/my.script1
I know PATH variable can be set so that this type of situation can be handled.
can anyone tell me or point me to how this can be handled, so that my script users execute the script by giving only the script name (my.script1) no matter in what folder they are?
I'm trying to set up a form mail script on a website that when Submitted, a cgi script is executed and a perl translator (located in a secured and inaccessible folder) translates the script. After speaking to my hosting provider, I was told to "Telnet into the system and make the script... (2 Replies)
hi guys
i give "ps -ef | grep some_executable_file" on the command line.
this "some_executable_file" resides on many paths which r included in the PATH environment variable, so the output depicts only "some_executable_file" in the COMMAND column. how can i get the full path?
thanx (3 Replies)
Dear list
its my first post and i would like to greet everyone
What i would like to do is select records 7 and 11 from each files in a folder then run an executable inside the script for the selected parameters.
The file format is something like this
7 100 200
7 100 250
7 100 300 ... (1 Reply)
Hello everyone,
I wrote a simple script (ksh) that I would like to be able to execute no matter where in the directory structure I am sitting at.
I typed echo $PATH to retrieve my path info and looking at that I decided the directory where to place my script. I copied the scripts to that... (3 Replies)
how to run an already developed script run against a list of ip addresses solaris 8 question.
the script goes away and check traffic information, for example
check_GE-VLANStats-P3 1.1.1.1
and returns the results ok.
how do I run this against an ip list? i.e a list of 30 ip addresses (26 Replies)
I have tcsh scripts on path
/home/chrisd/tatsh/trunk/hstmy/bin/tcsh/
I want to run the script from within another script.
Suppose I go to directory
/home/chrisd/tatsh/trunk/hsdata/n02/terr0.25/darwin
and want to run checksrdist.tcsh
So I do
cd ... (1 Reply)
i have a script running using variable defined in .profile
when i run that script manually its working
but when i run the same script through cron its giving path not found
I had defined path in .profile (3 Replies)
Hi
cannot find the path to a running process on a host.
I looked and tried some suggestions in forums to no avail.
can someone please help? I need to know where this process is starting from as we have several versions in multiple directories
--------- Process name
1201 1 0 Feb 14 ?... (14 Replies)
Hi all,
Recently i wanted to see if i have openssl installed in my system (solaris 10), so i do this (not sure if this is the right way to do this)
pkginfo -i | grep -i "ssl"
system SUNWopenssl-commands OpenSSL Commands (Usr)
system SUNWopenssl-include ... (3 Replies)
Discussion started by: javanoob
3 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)