Process 201 is cron. cron is started in the S75cron file in /etc/rc2.d. The sole purpose of this file is the graceful starting and stopping of cron. It checks for the file /etc/cron.d/FIFO and the process cron in the process table, and if cron is already running, will not execute an additional process. If cron is not running, it executes rm to remove /etc/cron.d/FIFO from the file system in case it exists, and executes a new cron process. Standard arguments apply.
Check to see if the 'cron' daemon is running.
There should be a process: /usr/sbin/cron that started at the same time as the system booted (check with who -b).
You can 'bounce' the cron daemon, if you want, with:
I am looking for information on how to process mail using a cron job. The email server is a hosted ISP, so I simply have a POP connection to the mailbox.
Specifically, I want to fire a cron job at {x} time and have pine, mail, mailx, or some other suitable mail client utility process the... (1 Reply)
Hi Experts,
Is there any command by which i can chk that the cron process is running fine? Say i have scheduled the cron to run at 10 o clock every monday,Do i need to wait for the time it runs and then chk using ps -ef?
Please shed some light.
Thanks
Ashok. (2 Replies)
I have script whether a cron daemon is running or not. Ive kept this script in cron to check. If the cron fails how ll i come to know that the cron daemon is failed. Mystery ...
Thanks
Gopi (2 Replies)
Hi All,
I have got a shell script that excutes some job and mails me the output as an attachment.
While running the script manually, its perfect.
when i am scheduling the job through crontab, i am getting the mail.
but the attachment but this is a blank file.
after the scheduler run, i can... (2 Replies)
Hi all,
We use cron "/usr/rdl/sc/cccron" to execute our jobs.
But sometimes it is being changed. but we are not sure when it is changed.
how could we find when cron is modified.
i checked cron by giving ls -l . but it is showing 2009 year.
ls -l /usr/rdl/sc/cccron
-r-xr-xr-x 1... (0 Replies)
Hi all,
We use cron "/usr/rdl/sc/cccron" to execute our jobs.
But sometimes it is being changed. but we are not sure when it is changed.
how could we find when cron is modified.
i checked cron by giving ls -l . but it is showing 2009 year.
ls -l /usr/rdl/sc/cccron
-r-xr-xr-x 1... (2 Replies)
I have process1 running on one machine and generating some log file. Now another process which can be launched on any machine wants to know if process1 is running or not and also in case it is running it wants to stream the logs file generated by process1 on terminal from which process2 is... (2 Replies)
Hello All,
I was wondering if someone could take a quick glance at this Cron job and tell me if it's going to do what I am expecting.
I want it to run everyday at 8:00 am and 5:00 pm.
And the line in Crontab looks like:
0 8,17 * * * /usr/local/myScript.sh
Does that look correct?
... (6 Replies)
Hi,
How can I write a cron job that runs the MySQL "show processlist" command and stores in log file every 5 seconds between 5 am to 7 am?
I know the lowest possible timing I can have in cron is a minute not second. If I need a script, I am looking for a solution in Bash.
I think this cron... (2 Replies)
Discussion started by: riomario
2 Replies
LEARN ABOUT XFREE86
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)