Every 15 minutes my script does:
So most of the time I don't want an email every 15 minutes that the script ran and logged to the db, just if the temp is high.
Sorry, but that's no script. That is a plan after which to write a script, at best. Most probably your script bears Cron Problem Number One, but that is just a wild guess as long as you post rubbish instead of your failing script.
Does any one knows a work around for the crontab bug when connecting using ssh to a Solaris 8 system?
When you submit a crontab job through a ssh session, the job will not be executed, SunSolve has reported no fixing patches? (3 Replies)
Hi
..first post !
I have a Unix v445 using solaris 10. I've trolled through various web pages but can't find exactly what I'm looking for.
I have an alert log...or any messages file for that matter I need to check for certain key (error type) phrases - if I find them, they are redirected to... (11 Replies)
Hi,
I am having trouble with this script. It is suppose to send me an email when the specified tablespace is 60% full. I run it but nothing happens
FREESPACELOG=/home/oracle/scripts/bin/free_space/freespace.sql
email=bob@bob.edu
subject="PROD: Tablespace Free Space"
cmd="mailx -s... (1 Reply)
hi all,
how do i email a file in the body of an email rather than as an attachment ??
have a ksh script which i need to read a file and email as part of the body rather than an attachment.
my code is :
uuencode file.log | mailx -s "test"
but this sends file as an attachment.
... (2 Replies)
Hi there,
I'm using crontab to move some files every minute, but when crontab doesn't find these files it sends a message to the file "user_name" in the directory "var/spool/mail". Is it possible to "bypass" this problem?
Thanks in advance,
Giordano Bruno (1 Reply)
Hi there,
I'm working with two servers, one with FEDORA 6 and the other one with FEDORA 7, and if I put these lines in crontab:
MAILTO=MYADDRESS@mail.com
*/1 * * * * df -h
everything works fine on FEDORA 7 , while it doesn't work on6?!?...and I find this message in the log file:
MAIL... (2 Replies)
Hello Guru's
I'm trying to take the output of solaris top command and output to a txt file every few minutes. The issue that I'm experiencing is that I can run the following:
#!/bin/bash
#
logfile="/usr/mvf/morris/top.log"
# echo... (2 Replies)
HI,
I am using centos 6 and finding difficultly in doing 2 below things.
1. i have a user praveen i want to allow him to create cron job of his own. so i have added his user id in cron.allow but still it is not allowing him to edit(even if i have created praveen from root user) or create his... (4 Replies)
Hi All,
The following databse table maintains
VENDOR and EMAIL details.
VENOR_NAME VENDOR_EMAIL
DELL surendra@dell.com
HP rajkamal@hp.com
ACER sumathi@acer.com
NOKIA kunal@nokia.com
SONY sinu@sony.com
We have to find emaild id of a vendor based... (7 Replies)
Discussion started by: ROCK_PLSQL
7 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)