You might consider using the "code" constructs when posting scripts. It keeps the script bit in a mono-face font and doesn't break lines. Like that @ line that follows the sqlplus line. Is that supposed to be on its own line or part of the line above it?
When you create a message, click on the pound sign (#) icon above the text and you'll get a code dialog box. I think most people who have experience posting know about the CODE constructs and just type them in (along with QUOTE, URL, and IMG constructs). They work very much like HTML coding except instead of using less than and greater than signs (<>) they use open and close brackets ([]).
I wrapped your script in the code constructs and then cleaned it up the way I might write the script. I didn't see any syntax errors but I also don't see the beginning of the script (should start with a #!/bin/ksh for example). There's a "done" statement with no start so it's hard to say if there are other errors we're not seeing.
Since the log file should still be where ever it is, you should be able to run the mail command by itself and see if it works. If you're running it out of cron, you might not have mail in your path.
Additionally your log could be anywhere. I'd normally have the full path for a log file and even set it in a variable (like $LOG) to make it harder to generate a typo.
You might consider putting the whole script in place. Also you can put a "set -x" at the beginning which turns on additional output that might tell you where your script is failing.
Hi all,
I am writing a script to monitor some processes existence in the system. It works perfectly by running the script manually in commend line. However, when I put it under cron to run it failed. Everything time when the variable is null in the if statment. it failed and quitted. Here is... (2 Replies)
I have created a script to strat and shutdown Oracle 10g DB on Solaris automatically when UNIX reboot. In the begining, it worked well. All of sudden, the dbstart part didn't work, other 3 part for lsnrctl, emctl, isqlplusctl all worked fine. I think it was TNS_ADMIN variable got problem. Because... (0 Replies)
Hello,
I am learning to debug in sgi-Irix6.5, after a core dump, I was adviced to perform a "strace", but I got the following information:
ERROR: tracer already exists
what shall I do now?
Thanks a lot
Daniel (0 Replies)
Hi
This is what I was trying to do, comment one line and add something different in a new line right next.
This is the command I want to do
more .profile | sed 's,STRING1, #STRING1 NEWLINE STRING2,'
(I´m using ',' because my string is something like this
exec... (3 Replies)
I have a good foundation of c++.I want to learn to program for linux/unix,can you give me some advises,for example classic books ,which operating system is used better(freebsd,solaris,federal linux.etc),and which aspects uses mostly in job.Can you give me clear direction for working or learning. (1 Reply)
Continuing saga of working on making a retail store more robust by creating a backup clone of the main server, a 1995 era :eek: PC running SCO OpenServer 5.0.0b and a discontinued Point of Sales (POS) software system.
I have a PC of the same make and model. The CPU runs faster and it has a... (5 Replies)
All,
I have a need for a portable shell script for LInux and HPUX. The script has a simple need; Check for local files of a specific name (i.e. filename*), scp them to another system, and archive them to a folder. The script runs via cron.
I first wrote the script in Linux (bash with gnu... (4 Replies)
Hello,
Here is my crontab
# Reboot one Sunday out of 2 at 02:00
0 2 * * 0/2 /usr/bin/reboot
2017-04-16
2017-04-23
2017-04-30
and so on
I tested my crontab here, it seems to work
Http://cron.schlitt.info/index.php?c...=100&test=Test
However on my distrib linux mageďa
When I register... (4 Replies)
I have prepared a shell script to find the duplicates based on the part of filename and retain latest.
#!/bin/bash
if ; then
mkdir -p dup
fi
NOW=$(date +"%F-%H:%M:%S")
LOGFILE="purge_duplicate_log-$NOW.log"
LOGTIME=`date "+%Y-%m-%d %H:%M:%S"`
echo... (6 Replies)
Discussion started by: gold2k8
6 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)