12-09-2013
Cron jobs with same pid
Hello,
I have an AIX6.1 machine and i noticed something "strange" in the server.
I noticed that each day there are times where 2 or 3 different cron jobs are running with same process id. How can this happen? I thought that pid is always unique for each process.
Is it a problem having this behaviour or not?
Thank you
10 More Discussions You Might Find Interesting
1. Solaris
whats up,
Have some questions about cron jobs, I am fairly new to the unix os.
My cronjob sends all output to my mail, does anyone know how to redirect output to come out on the screen???
Thanks...... (6 Replies)
Discussion started by: lewisoco
6 Replies
2. Solaris
I'm trying to run cron jobs to start any inhibited processes after a system reboot.
I can schedule th cron, but i'm confused as to how to incorporated the reboot, since reboot is scheduled at different times, once every month.
How can I write this to start every 15 min after after a reboot
... (2 Replies)
Discussion started by: Remi
2 Replies
3. Linux
I created a php script.
I'd like to have it run as a cron job every day at 10:30am. So i added
30 10 * * * /script.php to the cron file
Is it possible to run the script on the command line to test it out ? (1 Reply)
Discussion started by: dannyd
1 Replies
4. Solaris
how to Put a cron entry which should be same script triggered on every Saturday and 1st of every month at 01.00 GMT.
0 2 1 * 6 --( At 2.00 GMT every sat & on 1st of every month)
the above syntax is correct?
Thanks (1 Reply)
Discussion started by: kurva
1 Replies
5. Linux
Hi,
I am a Linux administrator (newbie) in my company. The distro being used in the servers here is Centos 5.3
Just need to know, as a Linux administrator is it better for me to use /etc/crontab to set my cron jobs. I do not want to use the crontab -e to schedule my cron jobs.
That means... (1 Reply)
Discussion started by: anaigini45
1 Replies
6. Shell Programming and Scripting
Hi Frenz,
How do we get a cron job running in background to foreground ? (3 Replies)
Discussion started by: mkalase
3 Replies
7. Shell Programming and Scripting
Hi,
please help on this am trying to exec the below mentioned cron jobs
but its getting failed fro the past two days
###but when am trying to execte the cron by the times
23,29 18 * * * /export/home/inrvgo/thelak/China.sh
its getting exec properly
please help on this
#... (8 Replies)
Discussion started by: thelakbe
8 Replies
8. Solaris
There are two jobs in Solaris , Cron and at jobs..
I know how to disable or enable cron jobs.
How can I enable at jobs and disable it.
Kindly help.
Rj (2 Replies)
Discussion started by: jegaraman
2 Replies
9. Red Hat
I'm running cronjobs on a redhat 5.X. Cronjobs are getting failed frequently so how to find the root cause (2 Replies)
Discussion started by: karthik9358
2 Replies
10. Shell Programming and Scripting
How to see which cron jobs are not running? (2 Replies)
Discussion started by: rahul.raj1989
2 Replies
LEARN ABOUT OSF1
queuedefs
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)