12-21-2004
First way to test a script is to execute it on the command line...if that succeeds then you should be able to run it from cron...
sometimes you might need to add a line "set -x" to test and see where your error is.
10 More Discussions You Might Find Interesting
1. Solaris
I have a cron job set to run a script everyday. If I run the script out side of cron it runs correctly. If cron runs the script is produces a 0 byte file and it puts the output in the / directory. The script is set to put the output in a specific directory. Any help would be appreciated. (8 Replies)
Discussion started by: mbattreall
8 Replies
2. Shell Programming and Scripting
Hi,
I have a script that's being called via a crontab which is a wrapper script that creates a log for the script that gets executed. Within the script that gets executed, it also run's subscripts. I've been able to get everything to work .. but the issue is one of the subscript that goes out... (4 Replies)
Discussion started by: primp
4 Replies
3. UNIX for Dummies Questions & Answers
I am attempting to run a cron job, however, I receive this cron output error:
Error: of parameter : xxxxx does not make a valid output file.
What causes this? (4 Replies)
Discussion started by: AM1234
4 Replies
4. Shell Programming and Scripting
Hi,
I have ascript which drops a mail with the jobs status.
here is the script:
#!/bin/ksh
mypath=/home/gaddamja
flashlogpath=/sbcimp/dyn/data/flash/log
cd $mypath
v1=`ls -lrt | grep -i checkFilesForAmber_EUR1. |tail -1 | awk '{print $8}'`
v2=`cat $v1`
cd $flashlogpath
... (1 Reply)
Discussion started by: jagadish_gaddam
1 Replies
5. Red Hat
I have the following cron task set to run every 15 minutes to ascertain how many users are in the system and append the result to the log.
/home/pronto/cus/whoisinc >> /home/pronto/cus/whoisin.log
This is the whoisinc script
date +"%d-%m-%Y,%k:%M,Pronto Users,`prowho -s | grep -v... (1 Reply)
Discussion started by: scottm
1 Replies
6. Shell Programming and Scripting
I can do this from the command line:
/home/mylogin/tests/script.sh > /home/mylogin/tests/`date +"%Y%m%d"`log.csv
It yields a file named: 20110429log.csv
I would like to schedule with cron to run daily.
when I enter the same line, as above in cron:
10 16 * * *... (3 Replies)
Discussion started by: landog
3 Replies
7. Shell Programming and Scripting
how to run a script using cron job and send the output as attachment via e-mail using unix. please help me.
how my cron job entry should be?
As of now my cron job entry is to run the script at specific time,
15 03 * * * /path/sample.sh | mail -s "Logs" email_id
In the above entry, what... (8 Replies)
Discussion started by: vidhyaS
8 Replies
8. Shell Programming and Scripting
Hi All,
I am running the below shell script through cron and surprisingly it gives different output
$uname -a
Linux 2.6.18-194.3.1.7.3.el5xen #1 SMP Fri Jul 30 00:08:45 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
$ echo $SHELL
/bin/bash
shell script:
cat sar_cpu.sh
#!/bin/bash
... (10 Replies)
Discussion started by: a1_win
10 Replies
9. UNIX for Advanced & Expert Users
Hi All,
I have a script which checks the status of HP Smart Array & then emails me the output.
The script run fine when executed manually but I receive no output when configured in a cron job.
The script is below:
hpacucli ctrl slot=3 show config | mail -s "ARRAY STATUS-`date`"... (6 Replies)
Discussion started by: coolatt
6 Replies
10. UNIX for Dummies Questions & Answers
Hello gurus,
I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired
report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup
is shown below:
#!/bin/ksh
db2... (3 Replies)
Discussion started by: okonita
3 Replies
LEARN ABOUT DEBIAN
specrb
SPECRB(1) SPECRB(1)
NAME
specrb - standalone test runner for test/spec and Test::Unit test suites
SYNOPSIS
specrb [OPTIONS] [FILES | -a ] [-- untouched arguments]
DESCRIPTION
The Ruby script specrb allows you to run tests written with test/spec from the command line. It can also be used for plain Test::Unit test
suites. You can either specify the names of the test files you want to run, or let specrb find automatically all the tests in your project,
by using the -a switch (see TEST/SPEC OPTIONS below).
You can also use various options on the command line to pass parameters to the Ruby interpreterm or to modify the behavior of test/spec
and/or test/unit.
RUBY OPTIONS
-e, --eval LINE
evaluate a LINE of code
-d, --debug
set debugging flags (set $DEBUG to true)
-w, --warn
turn warnings on for your script
-I, --include PATH
specify $LOAD_PATH (may be used more than once)
-r, --require LIBRARY
require the LIBRARY, before executing your script
TEST
/SPEC OPTIONS:
-s, --specdox
do AgileDox-like output
--rdox
do AgileDox-like output with RDoc formatting
-a, --automatic
gather tests from ./test/, include ./lib/
TEST
::UNIT OPTIONS:
-n, --name NAME
runs tests matching regexp NAME
-t, --testcase TESTCASE
runs tests in TestCases matching regexp TESTCASE
COMMON OPTIONS
:
-h, --help
show a message similar to this manpage
--version
show version
AUTHORS
The test/spec library has been written by Christian Neukirchen <http://purl.org/net/chneukirchen>.
This manual page, inspired by the help message of specrb, has been written for the Debian Project by Cedric Boutillier (but may used by
others).
2012-06-26 SPECRB(1)