Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Crons -Last run time and errorlog Post 302434449 by ashok.k on Friday 2nd of July 2010 03:32:04 PM
Old 07-02-2010
Crons -Last run time and errorlog

Hi

There are few crons running under my account. How to check the last run time of the Cron and if it has run successfully without any errors.

Also if there are any errors while running, will the errors be stored some where?

How to check the status of all the Crons?

Thanks
Ashok
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Crons executed multiple times.

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

Porblem with errorlog

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

Figuring out Crons

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

Multple crons at boot

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

run script for given time

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

last run time of any script

how to find when last time a scrit has ran? (7 Replies)
Discussion started by: RahulJoshi
7 Replies

7. UNIX for Advanced & Expert Users

Redirect ErrorLog to a script

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

Working With Crons

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

Forwarding AIX syslog/errorlog to remote SQL DB

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

Execution Problems with Crons

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
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)
All times are GMT -4. The time now is 06:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy