08-06-2003
Call me stupid but I thought I had tried everything before posting. I got it to work, I was using /bin/csh in the script but /bin/sh in the cronjob. Added "SHELL=/bin/csh" and now it works.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I wrote a script to test many systems to see if they are up or not. if a system is down, i am notified by email
now, most of the time,when systems are down in my enviroment, it is because the user accidentally or purposely (not knowing the consequences) hit the power button. so these problems... (3 Replies)
Discussion started by: TRUEST
3 Replies
2. Shell Programming and Scripting
Hi All
I want to run a script every half an hour everyday, but it looks like it is not working the way it is supposed to.
I use the line
0,30 * * * * ksh /...<script>
But it only runs every hour at 30 minutes.
Am i doing something wrong ?
I use AIX 5.1 as my OS.
Thanks In... (1 Reply)
Discussion started by: kswaraj
1 Replies
3. UNIX for Dummies Questions & Answers
I can ping by ip address but not by host name
everything is on the same subnet
check all of the normal files
I can telnet in to the unix box but can not open a connect to
the share dir.
unix ver sunSO 5.9
all the other computers ar Windows XP (with firewall turn off)
Thanks... (1 Reply)
Discussion started by: vviscomi
1 Replies
4. Shell Programming and Scripting
hi all,
have no experience with cronjob at solaris,
i have create script like below:
#!/bin/sh
DAY=`/export/home/oracle/bin/lastdate | nawk '{print $1}'`
/export/home/orahome/bin/sqlplus -s abc/abc<<eof
set heading off;
set linesize 100;
set feedback off;
spool... (4 Replies)
Discussion started by: bucci
4 Replies
5. IP Networking
Comp1=192.168.100.2
Comp2=192.168.100.6
both the comp have win2000 Os.
Using Cross cable i have connected back to Back.
When i ping From Comp1 to Comp2 its working fine.
But
When i ping From Comp2 to Comp1 its not working.
I know don't know what went wrong please help me out.... (4 Replies)
Discussion started by: ashokmeti
4 Replies
6. Solaris
Can someone tell me how I can get the following bolded output without having to issue the control C key when a ping is running?
ping -s cca-wl6
PING cca-wl6: 56 data bytes
64 bytes from cca-wl6: icmp_seq=0. time=0.796 ms
64 bytes from cca-wl6: icmp_seq=1. time=0.581 ms
64 bytes from... (5 Replies)
Discussion started by: SkySmart
5 Replies
7. AIX
Hi All,
I'm testing ping command on two servers.
A,B,C,D are servers
From A-->B:
ping -c 3 -p ff -s30720 <B IP-Addres>
This works fine.
From C-->D:
ping -c 3 -p ff -s30720 <D IP-Addres>
This is NOT working and 100% packe loss :(
But if I use 8700 instead of 30720 for packet size... (6 Replies)
Discussion started by: saraperu
6 Replies
8. Solaris
Hi friends,
I am running Solaris 10, which is connected to a DSL router running DHCP. During the installation I chose not to use DHCP and assigned a permanent IP address to solaris machine. I also did not choose any name service as well. The rest of the details are as under.
Solaris Machine
IP... (4 Replies)
Discussion started by: gabam
4 Replies
9. UNIX for Advanced & Expert Users
Hi,
I have a couch Db server running. I have written a script which will check and kill the multiple instances of the same and then start again a new one.
Now when i start the db server manually, the UI of the DB is accessible via browser. But when i do the same using cronjob, the UI of... (0 Replies)
Discussion started by: sarath@123
0 Replies
10. Shell Programming and Scripting
How can I get the following result of the "ping" command?
Example:
root@OpenWrt:~# ping google.com -c1 | sed -n 1p
PING google.com (216.58.210.14): 56 data bytes
How can I get the data only in the range of ()?
The result of what I want to get it:
216.58.210.14
Please use code... (4 Replies)
Discussion started by: andrewxxx
4 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)