11-13-2014
Yes oracle user has the permission to write in that log.
but no log file is even created which means it didn't run at all.
how to check system log+ also we dont receive mails
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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)
Discussion started by: hkapil
1 Replies
2. UNIX for Dummies Questions & Answers
Hi
I have a perl script which used 'glance' command to return all the processes with the thread count.
It is working fine when it is executed as a command, but as a crontab entry, the perl script is not getting executed.
thdcnt.pl
#!/usr/bin/perl
my $cmd=`glance -bootup -adviser_only... (1 Reply)
Discussion started by: manaac
1 Replies
3. UNIX for Dummies Questions & Answers
how to schedule a job in cron on last sunday of every month?:mad: (1 Reply)
Discussion started by: tp2115
1 Replies
4. UNIX for Dummies Questions & Answers
Hi I am trying to test the crontab entry by setting time as below ( set ahead more than 3min before saving the cron)
crontab entry:
30 15 1-27 * * && (cd /scripts;./script.csh.prod.UAT /dev/null 2>&1)
But this is not working, but below one is working.
30 15 1-27 * * (cd... (1 Reply)
Discussion started by: jramesh1
1 Replies
5. Shell Programming and Scripting
Hi,
How to add a cron job in /etc/crontab using a shell script.??:confused:
Actually the requirement is we need to run a script say, XXX.sh every 10 min through “cron”.
That can be achieved by adding the below code line in the /etc/crontab , (i.e., “crontab -e ” command to add this to the... (4 Replies)
Discussion started by: Dedeepthi
4 Replies
6. Solaris
Hi,
I have added the script entry into crontab by using crontab -e.
30 * * * * /scripts/info.pl $HOME/GCSS/logs > /dev/null 2>&1
But its not working yet.
Note: When i was added the script by the time I have faced issue as below
1) If I use crontab -l then i got cant open the script. ... (2 Replies)
Discussion started by: Mani_apr08
2 Replies
7. Solaris
Hi ,
I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility )
I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And... (4 Replies)
Discussion started by: chidori
4 Replies
8. Shell Programming and Scripting
Hi All,
i have a folder in a server say xxx.xx.xx.xx\abcd\efgh. i want to make a cron job entry so that i would get a mail (me@example.com) on business days. will this help me...
30 4 * * 1-5 cd \abcd\efgh|ls-ltr|mailx:me@example.comhttps://www.unix.com/images/editor/code.png (10 Replies)
Discussion started by: mahesh300182
10 Replies
9. Shell Programming and Scripting
Hi Gurus,
I am trying to connect to remote host from current host to check crontab entries. I have started like this
ssh -n -l db2psp 205.191.156.17 ". ~/.profile >/dev/null 2>/dev/null; cd log ;ls | wc -l"
I got this error ?
ssh: connect to host 205.191.156.17 port 22:... (1 Reply)
Discussion started by: rocking77
1 Replies
10. Solaris
Hi
I have one entry in my crontab that do not run, in cron, but it runs manually:
53 7 * * * /moneta_polled01/download/./get_dealer.sh
55 7 * * * /moneta_polled01/download/./mov_dealer.sh
The first entry do not run automatically, but it runs manually.
The second entry runs... (12 Replies)
Discussion started by: fretagi
12 Replies
LEARN ABOUT PLAN9
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)