It maybe because of the PATH variable not getting loaded.
Try giving the full paths to your commands instead of just the commds.Like, instead of just giving echo give
Try giving the full path to all your commands
Hi All,
I want to run a cron job to run on the first saturday of each month at 1:30am. Would the following entry suffice this condition
30 1 6 * 6 wall %Will this work%
Appreciate your time. (1 Reply)
Hi,
I am facing this problem . My Cronjob entry is not running !!!
I am having Sun solaris 9 and cronjob entry is
"45 1 * * * /safedir/rdns/opt/RDNS1.1Scripts/drpl_audit_log_script.sh_orig > /dev/null 2>&1"
Now when I try to look in the output log files it creates, it is some file with... (1 Reply)
Hi,
Where can we find Cron job logs?i have a cron job which is not executing at all,
00 12 * * * /xx/yy/job > /pp/qq/log
if i execute the job alone,it is executing fine.
>/xx/yy/job > /pp/qq/log (is executing fine)
but its not executing when it triggered from cron.is there any place cron... (7 Replies)
Hi folks,
I have got the following cron entry ...
08 30 * * * /mp1/scripts/test.sh > /mp1/scripts/test_logs.txt 2>&1
The problem is that instead of generating a new test_logs.txt file every time it keeps on appending the outputs to the test_logs.txt file. What is it that I am doing wrong... (2 Replies)
Hello All,
Anybody please help me to know ,what happens when a user having entry in both cron.allow and cron.deny files.Wheather the user will be able to access the crontab???
Thanks in advance
Vaisakh (5 Replies)
Can someone please quickly respond to this?
I need to have a script test.sh to run every 30 minutes from Monday to Saturday from 6am to 10pm as a crontab entry...
Thanks. (3 Replies)
Hi,
I need some clarification on cron entries. I have a cron job like..
15 01 19 02 6 exec /usr/bin/test.ksh
and I have another cron entry added, which is
15 01 20 02 6 exec /usr/bin/test.ksh
So, I am thinking the second cron entry shouldn't have run because 02/20 is Sunday, but... (1 Reply)
Hi,
I have to add two cron entry now. Please correct me if anything wrong
Below script should run at every one and half hour.
30 01 * * * /export/home/gxadm/scripts/collect_mq_info.pl $HOME/GCSS/logs > /dev/null 2>&1
Below script should run at every 2 hours
0 02 * * *... (9 Replies)
I have put a cron entry in oracle user for taking hot backup every wednesday@ 2.30 AM and have given the cron entry
30 02 * * 3 /u01/vijay/hotbackupcron 2>&1 >> /u01/vijay/hotbackup.log
also find below the script inside hotbackupcron, i have put in env variables as well
... (13 Replies)
Hi
I have a system running solaris 11, in which I am able to execute a script from the command line, but once I put i the crontab does run, but do not give results.
The entry is:
15 11 * * * /var/oswbb/./startOSWbb.sh >> myjob.log 2>&1
30 11 * * * /var/oswbb/./stopOSWbb.sh
I have check... (2 Replies)
Discussion started by: fretagi
2 Replies
LEARN ABOUT SUNOS
echo
echo(1B) SunOS/BSD Compatibility Package Commands echo(1B)NAME
echo - echo arguments to standard output
SYNOPSIS
/usr/ucb/echo [-n] [argument]
DESCRIPTION
echo writes its arguments, separated by BLANKs and terminated by a NEWLINE, to the standard output.
echo is useful for producing diagnostics in command files and for sending known data into a pipe, and for displaying the contents of envi-
ronment variables.
For example, you can use echo to determine how many subdirectories below the root directory (/) is your current directory, as follows:
o echo your current-working-directory's full pathname
o pipe the output through tr to translate the path's embedded slash-characters into space-characters
o pipe that output through wc -w for a count of the names in your path.
example% /usr/bin/echo "echo $PWD | tr '/' ' ' | wc -w"
See tr(1) and wc(1) for their functionality.
The shells csh(1), ksh(1), and sh(1), each have an echo built-in command, which, by default, will have precedence, and will be invoked if
the user calls echo without a full pathname. /usr/ucb/echo and csh's echo() have an -n option, but do not understand back-slashed escape
characters. sh's echo(), ksh's echo(), and /usr/bin/echo, on the other hand, understand the black-slashed escape characters, and ksh's
echo() also understands a as the audible bell character; however, these commands do not have an -n option.
OPTIONS -n Do not add the NEWLINE to the output.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscpu |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), echo(1), ksh(1), sh(1), tr(1), wc(1), attributes(5)NOTES
The -n option is a transition aid for BSD applications, and may not be supported in future releases.
SunOS 5.10 3 Aug 1994 echo(1B)