Sponsored Content
Full Discussion: Cronjobs
Operating Systems AIX Cronjobs Post 73373 by Just Ice on Tuesday 31st of May 2005 02:15:51 PM
Old 05-31-2005
everytime i have cron issues where some jobs run but some jobs don't --- the first thing i do is check the paths of those jobs that failed ... if that is not the case, check the permissions of the start files and directories ...

... i know it sounds stupid but i've been scorched by minor details that i've overlooked before so i always start with the simple stuff ...
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

cronjobs

hi How can I add a cronjob to the crontab file? to execute a shel script named testScript.sh every day at 00:00. Thanks (3 Replies)
Discussion started by: tamer
3 Replies

2. UNIX for Advanced & Expert Users

Delete Duplicate Cronjobs

I set up same cronjobs in two different users to generate messages at 5:30 AM Not Its generating duplicate messages. I want to delete the cron entries set up in the first user, but I am unable to view the entries in that user. I tried to find the process Id, but its not showing any id Could... (2 Replies)
Discussion started by: nskworld
2 Replies

3. Shell Programming and Scripting

Setting cronjobs...

Hi, We have 4 jobs to be run every month on different times - * a daily job runs once in 2 days at 3PM *a weekly runs every thursday at 3PM * a monthly runs last day of month either 30 or 31st at 3PM * 4th job runs on 3rd of every month at 3Pm How can I set the crontab for these 4 jobs... (4 Replies)
Discussion started by: krworks
4 Replies

4. Linux

Cronjobs stopped working

Hi All, I am user of a Linux machine and I have approximatly 15 cronjobs scheduled in my crontab. Yesterday my administrator made LDAP active on my userid and all the things are doing fine after that. But all cronjobs for my user id stored in my crontab have stopped working after that. Could... (1 Reply)
Discussion started by: bisla.yogender
1 Replies

5. Solaris

cronjobs not running.

hi friends, how to check if the cronjobs is not running and how to make it run again. (1 Reply)
Discussion started by: cromohawk
1 Replies

6. Shell Programming and Scripting

cronjobs stopped working

Hello people, I had these cronjobs scheduled in some Unix boxes which were running fine until yesterday.But then the password was changed for that user id and then the jobs stopped working. As far as i know cron jobs run from super user. I am completely lost over here now. Thanks. (2 Replies)
Discussion started by: King Nothing
2 Replies

7. Shell Programming and Scripting

Setting up cronjobs

hello all, I have a shell script and I need to schedule it in crontab, I have the next line: 06 16 * * 1,2,3,4,5 /usr/bin/ksh /path/path/name.sh > /path/path/name.log first, I scheduled from Monday to Friday but it doesn't run, the log file is empty.. any idea why is causing this?... (14 Replies)
Discussion started by: Geller
14 Replies

8. UNIX for Dummies Questions & Answers

Is this possible with cronjobs?

Hi there, i've a question about cronjobs. I'm creating a concept for a centralized logging repository using log4j/log4net. Sadly the appenders I want to use (fileappenders) aren't telegram based but need a permanent stream to the repository. Because I can not assure this I want to log these... (6 Replies)
Discussion started by: collatz
6 Replies

9. UNIX for Advanced & Expert Users

cronjobs orphan processes

Our cron job stats its started on Oct20 % ps -ef | grep cron root 1442044 1 0 Oct 20 - 25:23 /usr/sbin/cron All the below jobs aixmf,aixgh are triggered from cron only. user pid ppid date time cmd gaix 1581282 1 35 16:33:01 - 20:56... (1 Reply)
Discussion started by: karnan
1 Replies

10. Solaris

How to find all Cronjobs?

Hey Guys, i've got a big issue... I've to find all running scripts in all crontabs. Is there a possibility to display all crontabs of each user? What i've already tried? The following script: for user in $(cut -f1 -d: /etc/passwd); do crontab -l $user; done I'm already root but i didn't... (3 Replies)
Discussion started by: Marcusg562
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 08:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy