Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: cron problem
Top Forums UNIX for Dummies Questions & Answers cron problem Post 302226359 by kerpm on Monday 18th of August 2008 07:35:52 PM
Old 08-18-2008
cron problem
I'm using Red Hat and I need to get cron working and I'm not sure what the problem is. As a test I've done the following:

1) In /etc/cron.d I've created a file called date with the following contents
2) */1 * * * * root date >> /root/thedate
3) This works perfectly. It sends the date every minute to /root/thedate with no problem


Then when I tried the following, it would not work:

1) In /etc/cron.d I changed the file named "date" to contain the following:
2) */1 * * * * root /root/date.sh
3) The contents of /root/date.sh is the following:
#!/bin/sh
date >> /root/thedate
4) I chmoded /root/date.sh to 700 and was able to run it by executing ./date.sh
5) However, crond would not run this cron job and I am confused

Any help is appreciated.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cron problem

Hi, I want to run my shrip for every 30 min.. if i enter crontab -l i am getting following.. 00,10,20,30,40,50 * * * * /home/arbuser/temp2/perform/per.sh 00,15,40,35,50 * * * * sh home/arbuser/temp2/perform/per.sh if I enter like this : ps -ef |grep cron root 311454 1 0... (3 Replies)
Discussion started by: redlotus72
3 Replies

2. UNIX for Dummies Questions & Answers

CRON problem

I am having a problem running a shell within CRON. It will run successfully if I do not inject a .profile into the entry. However, the second I place a . profile in front of the shell, the job does not execute. Any ideas? (4 Replies)
Discussion started by: VooDooMan
4 Replies

3. AIX

Problem with cron

Hi all I am trying to run a job via cron, however it does not execute. The cron log file has the following lines in it. When I run the command at CL, it works. root : CMD ( su - JHOps -c $JHOPSROOT/exe/JHOPS15MIN.sh # Execute 15 minute collections ) : PID ( 516342 ) : Fri Nov 25 ... (2 Replies)
Discussion started by: jhansrod
2 Replies

4. UNIX for Advanced & Expert Users

cron problem!

The cron daemon on one of my HP boxes is giving the following error: I checked the queuedefs man page, and it has left me a bit confused. The man page says: So this means that no more than 100 cronjobs can be run at one time (we do not use at and batch on this system). The... (4 Replies)
Discussion started by: blowtorch
4 Replies

5. UNIX for Dummies Questions & Answers

Cron problem

Hi, I've just done a school boy error. I was trying to edit the crontab but instead of using: crontab -e I used crontab -r without realising. Then went to look at the crontab but ntohing their. Looked int he manual and -r removed the crontab. Is their any way of getting this back?? ... (3 Replies)
Discussion started by: tez
3 Replies

6. Shell Programming and Scripting

cron problem

Hi frnds... I m facing very irritating problem already waisted my 2 days.. I have a following script..( i am pasting only the main code) ftp -ivn 213.194.40.77 <<FTP user $user $password binary cd $FileDir/out lcd $localpath get $file rename $FileDir/out/$file $FileDir/tmp/$file... (7 Replies)
Discussion started by: clx
7 Replies

7. UNIX for Dummies Questions & Answers

Cron Problem

Hello folks, I've got a few cron jobs listed under a particular user id. They are running fine but then they are creating a new process every time they are running. Any idea folks? (3 Replies)
Discussion started by: King Nothing
3 Replies

8. Shell Programming and Scripting

Problem with Cron

Hi i am new here and have a quick question. i am receiving ./project.sh: line 12: syntax error near unexpected token `newline' ./project.sh: line 12: `echo "`date +"%F %R"` `md5sum /etc/passwd`" >> ' error message here is my script. could you please help! #!/bin/bash # PROGRAM:... (4 Replies)
Discussion started by: mas1888
4 Replies

9. Solaris

Problem with cron

Just wanted to know, what happens if a user exists in both files cron.allow and cron.deny. Will the user be able to set cron? Thanks, Deepak (7 Replies)
Discussion started by: naw_deepak
7 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

LEARN ABOUT OPENSOLARIS

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.11							    1 Mar 1994							      queuedefs(4)
All times are GMT -4. The time now is 09:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy