03-25-2015
Dont use relativ paths within crontab, use absolute paths instead. (as in your initial post)
hth
EDIT:
Or add the PATH env to crontab, put the script in such a path and just execute the script. (so the theory)
Either way, you have to make sure the script has execution flag set.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Why does this cron entry do nothing? It works interactively.
58 23 * * * mydate=`date '+%Y%m%d'`;mv /opt/home/user/file /opt/home/user/file_$mydate (5 Replies)
Discussion started by: steelrose
5 Replies
2. Solaris
HI all,
I would want to schedule a job to run every 2 weeks. In the mean time, i'm only able to schedule on every week. Is it possible to schedule 2 weeks on crontab?
Thank you. (3 Replies)
Discussion started by: *Jess*
3 Replies
3. UNIX for Dummies Questions & Answers
I set up a job to run a script in a certain directory to remove certain files. The script seems to run as my logs indicate but nothing happens. If I run the script manually then it removes the correct files. I'm now wondering if crontab doesnt have access to remove files from the directory I'm... (9 Replies)
Discussion started by: NycUnxer
9 Replies
4. AIX
My question is how to specify the one-time execution of a shell script in crontab?
For example: If I wanted to schedule shell "Test.sh" for one-time execution on December 13 at 8:00AM would it be as follows?
00 08 13 12 6 /usr/datatools/dtbackups/Test.sh > /usr/u/sybase_12.5/logs/Test.log &... (3 Replies)
Discussion started by: Alan.AIX
3 Replies
5. UNIX for Dummies Questions & Answers
Hello guys,
I have a server with Red Hat Enterprise Linux AS release 4 (Nahant Update 5), there i have a lot of users, im the root. I need to lock the use of crontab to the users, i mean, i dont want to give to the users the option to creat any crontab line, how can i do that?
I tried to... (4 Replies)
Discussion started by: lestat_ecuador
4 Replies
6. HP-UX
Please cna you tell me if the following command entered in error would affect the crontab file
crontab -e | more
Thanks :) (12 Replies)
Discussion started by: blondie2407
12 Replies
7. Shell Programming and Scripting
I have a user (xxx) who is allowed to run cron jobs when a job is
launched from cron is the .profile sourced in? I am not sure it is so I setup a cron job as this user to do the following:
35 15 * * 0-5 su - xxx -c "ksh ls -lt /tmp" > /tmp.out
and I am seeing the following error (see... (2 Replies)
Discussion started by: BeefStu
2 Replies
8. Solaris
I want to run a script on (say) the 4th friday every month. But if I include this line in the crontab :
45 9 22-28 * 5 echo '4th Friday'|mailx -s "Fri week 4" mike
it sends me mail if the date is 22-28, OR the day is friday. So I get mail every day for a week , and also every friday.
I... (2 Replies)
Discussion started by: mikejordan
2 Replies
9. UNIX for Dummies Questions & Answers
Hey out there
This is all I have in my crontab file. I know the crontab works because it was already out there and working. I simply replaced the existing with my line of code below to see if it worked. I uploaded 6 month old pdf files in this directory, stopped/started all the scripts that... (3 Replies)
Discussion started by: vsekvsek
3 Replies
10. Shell Programming and Scripting
Hello,
I have scheduled the execution of a file (delete_oldv02) every hour with crontab and it works perfectly. See below the instruction written.
0 */1 * * * /home/delete_oldv02 >>/home/delete_oldv02.log
My first question is if I can add one more line to crontab.
I also would like to... (5 Replies)
Discussion started by: dcaccount
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)