10 More Discussions You Might Find Interesting
1. Solaris
Hey Guys,
i've got a big issue... I've to find all running scripts in all crontabs. Is there a possibility to display all crontabs of each user?
What i've already tried? The following script:
for user in $(cut -f1 -d: /etc/passwd); do crontab -l $user; done
I'm already root but i didn't... (3 Replies)
Discussion started by: Marcusg562
3 Replies
2. Shell Programming and Scripting
Hello Everyone,
We have a cronjob scheduled to pick up files from one system and transfer to another system. the underlying code is a shell script. These cronjobs were working correctly until sometime. 2 days back they did not pick up the scripts but created empty logs. However when we tried... (6 Replies)
Discussion started by: Rads
6 Replies
3. UNIX for Dummies Questions & Answers
Hi there,
i've a question about cronjobs. I'm creating a concept for a centralized logging repository using log4j/log4net. Sadly the appenders I want to use (fileappenders) aren't telegram based but need a permanent stream to the repository. Because I can not assure this I want to log these... (6 Replies)
Discussion started by: collatz
6 Replies
4. Shell Programming and Scripting
Hello people,
I had these cronjobs scheduled in some Unix boxes which were running fine until yesterday.But then the password was changed for that user id and then the jobs stopped working. As far as i know cron jobs run from super user. I am completely lost over here now.
Thanks. (2 Replies)
Discussion started by: King Nothing
2 Replies
5. Solaris
hi friends,
how to check if the cronjobs is not running and how to make it run again. (1 Reply)
Discussion started by: cromohawk
1 Replies
6. Linux
Hi All,
I am user of a Linux machine and I have approximatly 15 cronjobs scheduled in my crontab. Yesterday my administrator made LDAP active on my userid and all the things are doing fine after that. But all cronjobs for my user id stored in my crontab have stopped working after that.
Could... (1 Reply)
Discussion started by: bisla.yogender
1 Replies
7. Shell Programming and Scripting
Hi,
We have 4 jobs to be run every month on different times -
* a daily job runs once in 2 days at 3PM
*a weekly runs every thursday at 3PM
* a monthly runs last day of month either 30 or 31st at 3PM
* 4th job runs on 3rd of every month at 3Pm
How can I set the crontab for these 4 jobs... (4 Replies)
Discussion started by: krworks
4 Replies
8. UNIX for Advanced & Expert Users
I set up same cronjobs in two different users to generate messages at 5:30 AM
Not Its generating duplicate messages.
I want to delete the cron entries set up in the first user, but I am unable to view the entries in that user.
I tried to find the process Id, but its not showing any id
Could... (2 Replies)
Discussion started by: nskworld
2 Replies
9. AIX
We recently upgrade from AIX 4.3.3 to AIX 5.3, We noticed that some cronjobs that run for our programmers did not fire off this morning. You can crontab -l and -e and see the jobs. Did AIX 5.3 change something?
Thanks
Mike (1 Reply)
Discussion started by: mcastill66
1 Replies
10. UNIX for Dummies Questions & Answers
hi
How can I add a cronjob to the crontab file?
to execute a shel script named testScript.sh every day at 00:00.
Thanks (3 Replies)
Discussion started by: tamer
3 Replies
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)