Sponsored Content
Full Discussion: Cron Problem
Top Forums UNIX for Dummies Questions & Answers Cron Problem Post 302276611 by King Nothing on Wednesday 14th of January 2009 08:12:45 AM
Old 01-14-2009
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?
 

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

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... (1 Reply)
Discussion started by: kerpm
1 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
queuedefs(4)						     Kernel Interfaces Manual						      queuedefs(4)

NAME
queuedefs - Queue description file for at, batch, and cron commands DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron or specifies other characteristics for cron. Each noncom- ment line in this file describes either one queue or a cron characteristic. Each uncommented line should be in one of the following for- mats. q.[njobj][nicen][nwaitw] max_jobs=mjobs log=lcode The fields in these lines are as follows: The name of the queue. Defined queues are as follows: The default queue for jobs started by at The default queue for jobs started by batch The default queue for jobs run from a crontab file Queues d to z are also available for local use. The maximum number of jobs that can be run simultaneously in the queue; if more than njob jobs are ready to run, only the first njob jobs will be run. The others will be initiated as currently running jobs ter- minate. The nice(1) value to give to all jobs in the queue that are not run with a user ID of superuser. The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that queue, or because the system-wide limit of jobs executing (max_jobs) has been reached. The maximum number of active jobs from all queues that may run at any one time. The default is 25 jobs. Logging level of messages sent to a log file. The default is 4. Defined levels are as follows: level-code level 0 None 1 Low 2 Medium 3 High 4 Full Lines beginning with # are comments, and are ignored. EXAMPLES
The following file specifies that the b queue, for batch jobs, can have up to 50 jobs running simultaneously; that those jobs will be run with a nice value of 20. If a job cannot be run because too many other jobs are running, cron will wait 60 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. If a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. b.50j20n60w The following file specifies that a total of 25 active jobs will be allowed by cron over all the queues at any one time, and cron will log all messages to the log file. The last two lines are comments that are ignored. max_jobs=25 log=4 # This is a comment # And so is this FILES
Main cron directory The default location for the queue description file. RELATED INFORMATION
Commands: at(1), cron(8), crontab(1), nice(1) delim off queuedefs(4)
All times are GMT -4. The time now is 07:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy