07-10-2015
Considering the orthography in your post, are you sure you ran test or tset in lieu? That would make a serious difference.
10 More Discussions You Might Find Interesting
1. BSD
I'm trying to understand what is happening.
The "setup".
System running OpenBSD 3.3
Connect to the system using PuTTy or with the SSH.COM SSH client, issue a DF command.
First line that comes back is:
Filesystem 1K-blocks Used Avail Capacity Mounted on
When I connect the the... (13 Replies)
Discussion started by: woodstone
13 Replies
2. Shell Programming and Scripting
Hi,
I have a script that's being called via a crontab which is a wrapper script that creates a log for the script that gets executed. Within the script that gets executed, it also run's subscripts. I've been able to get everything to work .. but the issue is one of the subscript that goes out... (4 Replies)
Discussion started by: primp
4 Replies
3. Shell Programming and Scripting
Hi All,
When starting an SSH tunnel, piped output 'hangs' (on AIX) :
ssh -Nf -Llocalhost:22000:server:22 proxy | cat -vet -
... hangs ...
Does anybody know how to prevent this?
Of course, in my script I don't use the tunnel as I do in the example above. In my script the call to ssh is... (7 Replies)
Discussion started by: whbos
7 Replies
4. Shell Programming and Scripting
Hello;
Am trying to generate runaway proc report using ssh thusly:
===================
ssh -t -t $BOX 'TERMINAL="vt100" top -d1 -h -n 10' >> $FILE
.
.
cat $FILE | mail -s "Latest Top `date`" $MAIL_TO
====================
But the output to e-mail comes out rather garbled ..
Any ideas... (1 Reply)
Discussion started by: delphys
1 Replies
5. Shell Programming and Scripting
Hello;
Am trying to correct the formatting of tail output over ssh.
Using the following code:
echo "" > $FILE
for BOX in $SERVERS
do
echo "Processing on $BOX" |tee -a $FILE
echo "===============================" >> $FILE
sudo ssh $BOX 'TERMINAL="vt100" /usr/bin/sh -s' <... (2 Replies)
Discussion started by: delphys
2 Replies
6. Shell Programming and Scripting
Hey Guys,
i have a script that generates logs at our isilon storage.
The part of the script is to geneate logs and grep its name:
VAR=`ssh -o UserKnownHostsFile=/dev/null root@XXX isi_gather_info | grep -i "Package:" | awk '{ print $2 }'` Now , while this is run, i do not see the status of... (2 Replies)
Discussion started by: anshulsahdev
2 Replies
7. Shell Programming and Scripting
The code below works ok, however; I need to output the results to a local variable
the_path="/mnt/back/hang"
ssh -T -i /home/buddy/.ssh/id_rsa buddy@ginger << EOF
find ${the_path} -name "*.jpg" | wc -l > ## output to local variable
exit
EOF (3 Replies)
Discussion started by: squrcles
3 Replies
8. Shell Programming and Scripting
Hi everyone, after about 2 days of scratching my head on this one, I'm finally ready to punt this and ask for some actual help. Here's the situation. We have 1 server, that runs multiple VM's. To gain access to those VM's we ssh from host01 to the other vm hosts. For example when we first log... (4 Replies)
Discussion started by: Lost in Cyberia
4 Replies
9. Shell Programming and Scripting
Hi, I need to get the output of ssh for multiple servers using for loop which is returning how many users are logged in, one below the other. But i'm getting output in single line for one of the servers.
XXXX pts/0 Oct 18 08:45 abcd pts/3 Oct 18 06:46 abcde pts/4 Oct 18 06:46 xyzqw pts/5 Oct 18... (14 Replies)
Discussion started by: sam_bd
14 Replies
10. Shell Programming and Scripting
Hi Folks,
I'm currently trying to read several values into different variables.
Actually, what I'm doing works, but I get an error message.
My attempts are:
read strCPROC strIPROC strAPROC <<<$(ssh -n -T hscroot@$HMC "lshwres -r proc -m $strIDENT --level sys -F \"configurable_sys_proc_units... (11 Replies)
Discussion started by: NKaede
11 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)