07-03-2010
in syslog you will be able to find out whether the cron ran the particular job or not.. but the error kind of thing you have to take care from the application side..
Only starting the said process in the time is the job of cron, it does not worries about any error.. and proceeds.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
For some reason my crons are being executed twice. Any suggestion?? I'm currently on 5.8 (2 Replies)
Discussion started by: shorty
2 Replies
2. AIX
hi all,
i am facing a problem that my error log was empty(0 byte).
i dont whether threr is any mistake or my server working that much nicly......
please find some output down.
# errpt
0315-180 logread: UNEXPECTED EOF
0315-171 Unable to process the error log file /var/adm/ras/errlog.... (1 Reply)
Discussion started by: rrlog
1 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I've built a news site using SimplePie to pull in a set of feeds and display them on a page. The caching is working but the problem is that the first initial load is slow. After that, you can hit refresh and it loads very quickly. I'd like to eliminate that first slow load by creating a... (2 Replies)
Discussion started by: eightgames
2 Replies
4. SCO
I am running SCO on a Netfinity system and two crons are started on bootup, but only after the system is brought down hard. i.e. running haltsys, reboot, or by a power outage. Has anyone seen this before and know a resolution to stop it? (0 Replies)
Discussion started by: ertzman
0 Replies
5. Shell Programming and Scripting
Hi!
I need to run my script for a specific number of time, as specified by the user: For instance, if the user specified 10, my script should run for until 10 seconds expire. How do I do this? (0 Replies)
Discussion started by: looza
0 Replies
6. Shell Programming and Scripting
how to find when last time a scrit has ran? (7 Replies)
Discussion started by: RahulJoshi
7 Replies
7. UNIX for Advanced & Expert Users
Hello, guys!
I need to redirect the error_log of apache web server to a script. I tried to use a pipe instead of a filename but this will cause me some troubles beacause cPanel doesn't like it. So, I would like to try something else.
Do you have any ideea on how can I read the content of the... (2 Replies)
Discussion started by: Sergiu-IT
2 Replies
8. Shell Programming and Scripting
It said I had to approve them through here or something because they won't work and everyone on my site Is gettin pissed off. Please help (3 Replies)
Discussion started by: hell-on-earth
3 Replies
9. AIX
Due to a project I'm currently tasked with I'm spending my time trying to find a way to forward the syslog to a remote, in this case Red Hat, server and squeezing it into a SQL DB.
Rsyslog is doing this job quite nicely for most of our test-servers, but I couldn't find any reliable information on... (1 Reply)
Discussion started by: Skleindl
1 Replies
10. UNIX for Dummies Questions & Answers
Buddies, cron is not executing any monitoring scripts for 'Oracle' user in Red Hat Linux 5.
Details about the cron job :-
oracle@localhost ~]$ crontab -l
15 7 * * * /home/oracle/tab.sh
The tab.sh script when firing manually is working fine.
Any inputs/advice will be great for me. (12 Replies)
Discussion started by: sandip250382
12 Replies
LEARN ABOUT HPUX
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and crontab
SYNOPSIS
DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
[njob[nice[nwait
The fields in this line are:
q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by
(see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined
queues.
njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see
cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed
by setting the variable to 1 in the file.
nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). 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 more than 100 jobs were running in all the queues (see njob above).
EXAMPLES
Consider the following file:
The file is interpreted as follows:
The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of
1.
Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds
before trying again to run it (see cron(1M)).
The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2.
If a job cannot be run because too many other jobs are running, 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 value of 2, and if a job cannot be run because
too many other jobs are running, will wait 60 seconds before trying again to run it.
SEE ALSO
at(1), nice(1), crontab(1), cron(1M), proto(4).
STANDARDS CONFORMANCE
queuedefs(4)