Sponsored Content
Full Discussion: Crontab is not working
Operating Systems Linux Red Hat Crontab is not working Post 302955304 by vbe on Wednesday 16th of September 2015 08:17:56 AM
Old 09-16-2015
Have you looked in your mails, cron logs to see if you find anything?
And without seeing your crontab line and the job you are trying to run, we cant help more than that, perhaps you can start by looking if that user is granted the right to use cron...
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

crontab not working right

I am having problems with a sparc5 solaris 7 box, when i try to edit cron, (crontab -e as root), it says $ crontab -e 0 and then nothing, if i enter anything it errors out but does accept q for quit. But doesn't bring up my editor of the cron file. How can I troubleshoot this? ... (3 Replies)
Discussion started by: kymberm
3 Replies

2. UNIX for Advanced & Expert Users

crontab NOT working

Hi, I have put the following entry in crontab and it is NOT working 1 * * * * && /mybin/myjob.sh As today is Sep 26th, Iam using NF-4 to test. Thanks (2 Replies)
Discussion started by: baanprog
2 Replies

3. UNIX for Advanced & Expert Users

crontab not working

Dear all We have SunOS 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V250 i have scheduled cronjob but its not working Crontab details 15 15 * * * /d5/oratest/testdb/hotbackup_new.sh TEST247 15 15 * * * mkdir -p rajesh /d4/appltest Crontab log details > CMD: mkdir... (4 Replies)
Discussion started by: rajesh_hv
4 Replies

4. Solaris

crontab is not working.

I have a script which name is sicaklik.sh It is in the root directory. I can run manually but I want to run automatically every 3 minutes but it is not working. WHY? #whoami root #crontab -l #ident "@(#)root 1.21 04/03/23 SMI" 3 * * * * sh ./sicaklik.sh #ls -l sicaklik*... (6 Replies)
Discussion started by: getrue
6 Replies

5. UNIX for Dummies Questions & Answers

crontab not working

Hi, I had setup crontab to execute my script every day midnight 00:00 Below are the current settings. crontab -l 0 0 * * * /apps/bin/compress.ksh_moht > /dev/null 2>&1 Should it not work? I need help fix this? (8 Replies)
Discussion started by: shifahim
8 Replies

6. Red Hat

crontab is not working!!

I can run manually script of ntopdump.sh but crontab can't run this script very five minutes. # crontab -l */3 * * * * root sh /root/ping.sh */5 * * * * root sh /root/ntopdump.sh # # pwd /root # ls -l total 88 -rwxrwxr-x 1 root root 1645 Jun 14 19:01 anaconda-ks.cfg drwxrwxr-x 2 root... (14 Replies)
Discussion started by: getrue
14 Replies

7. Solaris

crontab not working

Shell = ksh Hi all, I scheduled an automated job on my application server like below, 30 13 * * 1-5 $HOME/my_script.sh However the script was not executed as expected. Any reason that may cause this to happen? (6 Replies)
Discussion started by: isaacniu
6 Replies

8. UNIX for Advanced & Expert Users

Crontab not working, please help

Hi, When I set the crontab to run every minute, every hour, it works fine. * * * * * env > /tmp/env.output However I want to run it every day at 8:00 AM and it does not run. * 8 * * * env > /tmp/env.output I ran the 'date' command which says it's 8AM PST and also the 'TZ'... (0 Replies)
Discussion started by: samantha13
0 Replies

9. Linux

Crontab not working

Hi, I know this is a common topic. I'm trying to launch a perl script using a contab -e entry. I've been trying diff options but nothing seems to work: My cron is running: UID PID PPID C STIME TTY TIME CMD root 3755 1 0 Nov27 ? 00:00:00 crond This... (4 Replies)
Discussion started by: krebe
4 Replies

10. Shell Programming and Scripting

Crontab not working

Hi All, I have a script with deatils as : $ ls -ld catch_logs.sh -rwx--x--x 1 muser muser 752 Jun 5 22:36 catch_logs.sh User crontab looks likes: $ crontab -l SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin * * * * * /opt/scripts/catch_logs.sh Now if I run this script... (7 Replies)
Discussion started by: Junaid Subhani
7 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 01:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy