04-27-2016
cron is run with an extremely limited PATH environment, quite probably your script isn't finding commands its trying to run.
You might try something like
* * * * * . /etc/profile ; /path/to/script to get a more complete profile before running your script, or modify the script itself to set a more complete PATH value before you do anything else.
This User Gave Thanks to Corona688 For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
I have a shell script which works fine at the command line
and does works in crontab also but does not send the output to
mail as other scripts do by default.
10 1 * * * /export/home/test/report_script
by default should send the output to mail but the script
runs OK and the output... (1 Reply)
Discussion started by: run_time_error
1 Replies
2. UNIX for Dummies Questions & Answers
dear all ,
does any one now how can i become sure that the crontab that i put was working successfully not by looking for thr result of the sheduled task but from a log for the crontab or something similar
and i need to check that the cron i wrote is correct
00 15 * * 0,1,2,3,6... (2 Replies)
Discussion started by: habuzahra
2 Replies
3. UNIX for Dummies Questions & Answers
How can I run "crontab" (parameters) every 6 hours on solaris machine?
Thanks (1 Reply)
Discussion started by: gen4ik
1 Replies
4. Shell Programming and Scripting
i have a ksh script that creates messages in a temp directory and then sends them out using the sendmail command and i'm trying to set it up to run every night with crontab.
So the basic gist of the script is
#create temp dir and messages
...
#loop through each message and send using sendmail... (3 Replies)
Discussion started by: bob122480
3 Replies
5. UNIX for Dummies Questions & Answers
hi all
how to schedule the crontab file in unix? (2 Replies)
Discussion started by: ss4u
2 Replies
6. Shell Programming and Scripting
Hi All,
I've a shell script which calls a Sybase stored procedure to do some functionality. I want to schedule the running of this script by crontab. I'm using Solaris 5.8. When i executed the following command
crontab -l
i got the output as
crontab: can't open your crontab file
How... (10 Replies)
Discussion started by: sumesh.abraham
10 Replies
7. UNIX for Advanced & Expert Users
hi,
I run a .sh file using crontab. I need to know the path of the file . Previously when I run the file alone , i used "pwd" but now when using crontab it gives the temp directory of the file.
Is there any way I can find the absolute path of the file when i execute it ?
Regards,
Ranga (7 Replies)
Discussion started by: r_W213
7 Replies
8. UNIX for Advanced & Expert Users
Dear All
jobs are scheduled in crontab . To view this I use crontab -l . But suddenly today I am not able to see any jobs that is being scheduled in crontab. when I type crontab -l , I am seeing nothing.I am not logging through admin user(i dont have it).But I can schedule jobs through... (3 Replies)
Discussion started by: tkbharani
3 Replies
9. Shell Programming and Scripting
I have a crontab entry,but it is not working.
Can anybody help me in this regard?? (2 Replies)
Discussion started by: Sourav_Paul
2 Replies
10. UNIX for Dummies Questions & Answers
Hi, can someone explain the differences between using the at and crontab commands. When would you use one command over the other?
TIA
Dom (1 Reply)
Discussion started by: domburf69
1 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)