Sponsored Content
Full Discussion: Cron Daemon
Top Forums UNIX for Dummies Questions & Answers Cron Daemon Post 3902 by alwayslearningunix on Friday 13th of July 2001 09:35:35 AM
Old 07-13-2001
The cron daemon is the daemon which deals with job scheduling in UNIX. Jobs are scheduled via a flat ASCII text file called a crontab. If something goes wrong with a job that has been scheduled with cron then it usually sends a mail to the user concerned - check your crontab file for jobs that are running (crontab -l) edit it if need be (crontab -e).

The jobs that are running will give you better idea of where to goto troubleshoot the actual problem.

If you can't see any jobs scheduled bear in mind that a crontab can exist for any users, so su to a user you suspect would run a job and check their crontab file.

Regards.
alwayslearningunix
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cron daemon

I ve a problem with the cron daemon. i ve a process that sends many mail, and full my /var FS i don t want to write a script that would clean its mails i want to know if it would be possible to stop the cron daemon sending mails only for that specific process. Thanks !:D (3 Replies)
Discussion started by: karine
3 Replies

2. SCO

Stoping & starting the cron daemon

Hi We are running SCO ver 5. Recently the cron daemon stopped running on its own. How do I find out why? How do I restart/stop it? I typed cron but it didn't work. Will rebooting it do the trick or can I manually start and stop the cron daemon? Please help. Thanks & Regards. (0 Replies)
Discussion started by: othman
0 Replies

3. AIX

AIX and cron logs filtering ?: /etc/cronlog.conf, /var/adm/cron/log

Hi, I can use 'crontabs –e' and do all the scheduling I like. However I would like to auto send myself just the cronjobs logs that fail. That is to say the PIDs that fail and the related lines with those PID’s only. (Not the full set of logs) Has anyone done this work? Or does an AIX 5.3 tool... (0 Replies)
Discussion started by: Keith Johnson
0 Replies

4. UNIX for Dummies Questions & Answers

how execute/visit a site using the cron daemon?

hi, i need to execute/visit a site to check if the site is up or not i have a server that have cron shedule that can execute a php file now how can i execute/visite a site using the same way as i execute a file? thanks a lot for your help :) (1 Reply)
Discussion started by: jasonx22
1 Replies

5. Solaris

Mail is not sent by cron daemon

Hello All, In SunOS 10, I have some cron jobs and it is running fine but the cron job outputs are not mailing to any acount of the system. In other OS, we have option like MAILTO variable or /dev/null to disable but in Sun I have no idea how it is disabled by default and how do I... (13 Replies)
Discussion started by: Tlogine
13 Replies

6. UNIX for Dummies Questions & Answers

Cron Daemon and alert

I am not system admin on Unix or Linux server. I am Oracle DBA to work on these operating systems. On our Oracle Linux 5.8 box, it always pump up the alert message like this: Cron Daemon /bin/sh: /opt/oracle/product/middleware/agent11g/ccr/bin/emCCR: No such file or directory Please help... (2 Replies)
Discussion started by: duke0001
2 Replies

7. Fedora

cron daemon name

Hi All, Please tell me which daemon is responsible for start and stop the crontab. Please tell me the location where it resides in Linux platform. Sindu. (2 Replies)
Discussion started by: indira_s
2 Replies

8. Shell Programming and Scripting

Commented cron job -- cron monitoring

Hi I have a requirement to write a shell script,that will check the all commented job in cron job.Please help !! (2 Replies)
Discussion started by: netdbaind
2 Replies

9. Shell Programming and Scripting

Cron job - Need to run Cron every quarter at particular time

Hi, 1) If some job supposed to run on 1st of every month at 7 AM In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day? 2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct) And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies

10. UNIX for Dummies Questions & Answers

Execution problem with Cron: Script works manually but not w/Cron. Why?

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
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 07:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy