Sponsored Content
Full Discussion: Process time-to-live setting
Operating Systems Linux Process time-to-live setting Post 302241827 by edzillion on Tuesday 30th of September 2008 11:30:46 AM
Old 09-30-2008
Process time-to-live setting

I have a cron job scheduled to run every 5 mins, and run a php script.
Something was not right about the script and when I checked the server had very little spare memory.
Looked in running processes and I could see that many instances of the script were still running.
I am new to this whole linux admin thing, and I am using webmin. I have a few questions.
For each instance of this script there are three lines:

15339 root 15:36 CROND 15340 root 15:36 php /var/www/html/beta/assets_30.php 15344 smmsp 15:36 /usr/sbin/sendmail -FCronDaemon -i -odi -oem -oi -t
First, is there a diference between 'kill' and 'terminate' ?
How can I kill/term all three at once, since they are obviosly related? I am currently killing only the php script, (ok after getting rid of all the php entries all the sendmail ones dissapeared. ).
Why is there a sendmail process associated with the cron job (this job has nothing to do with sending mail)

Is there a way I can set a time-to-live on each script so that linux can kill the processes automatically in case they stall.
 

8 More Discussions You Might Find Interesting

1. Cybersecurity

time to live

i wondering about the ttl for the sshd on solaris 9 ... i read that you can change it to a different value to fool some OS "fingerprinting" tools such as queso or nmap. the default value is 255, i've tried to set it to 155 and 55 but nmap still see that port 22 is opend. do you know something about... (3 Replies)
Discussion started by: pressy
3 Replies

2. UNIX for Dummies Questions & Answers

how to Decrease priority of a particular process in time of process creation

how to decrease priority of a particular process in time of process creation... and also how to decrease priority of a particular process after process creation.. can any one please help me out... (2 Replies)
Discussion started by: Ramkum
2 Replies

3. Linux

Process start time not showing correct time

Process start time is not showing the correct time: I had started a process on Jun 17th at 23:30:00. Next day morning when I run the command "ps -ef | grep mq", the process is showing the start date of Jun 17th but the start time is 00:16:41 Day/Date is setup correctly on the server. It... (2 Replies)
Discussion started by: hemangjani
2 Replies

4. Web Development

Setting up Development and Live web site environment

Hi, I am fairly new to unix so please go easy on me.. I have a VPS on which I would like to setup a development and live web site environment and can't seem to work out what is the best technique for doing so. I would like to be able to mirror the live site and have a "check out" and... (0 Replies)
Discussion started by: ciantrius
0 Replies

5. UNIX for Dummies Questions & Answers

Live/real-time text-file updates in terminal

I want to have a terminal open and have something like a "repeating cat" command running in it for a certain text file (in particular /var/log/system.log). So my terminal will scan or cat the text file every so often or whenever the text file system.log gets written to by the system, it will... (1 Reply)
Discussion started by: guitarscn
1 Replies

6. Shell Programming and Scripting

How to calculate time difference between start and end time of a process!

Hello All, I have a problem calculating the time difference between start and end timings...! the timings are given by 24hr format.. Start Date : 08/05/10 12:55 End Date : 08/09/10 06:50 above values are in mm/dd/yy hh:mm format. Now the thing is, 7th(08/07/10) and... (16 Replies)
Discussion started by: smarty86
16 Replies

7. Red Hat

Setting Up live FTP Server with Static IP in Red-Hat Linux 6

Hi Guys, I want to some guidance from you in setting up the Live FTP server in Redhat Linux 6 with Static IP 120.50.150.50. Now should I set my Static Public IP directly to my Linux machine? If so what whould be my sunbet mask? Is any type of natting required here? if so where would... (2 Replies)
Discussion started by: manalisharmabe
2 Replies

8. Shell Programming and Scripting

How to process only new line of tail -f command from live log file?

Hi, I want to read a live log file line by line and considering those line which are newly added to file Below code I am using, which read line but as soon as it read new line from log file its starts processing from very first line of file. tail -F /logs/COMMON-ERROR.log | while read... (11 Replies)
Discussion started by: ketanraut
11 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 12:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy