12-08-2010
Quote:
Originally Posted by
Chubler_XL
How can $Now be both less than 705 and greater than 708?
I forgot to change the AND in OR when inverting the condition !
I Corrected the original post.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i have process that was started few days ago , is there way to know by its id how long it was alive in the system ?
Thanks (2 Replies)
Discussion started by: umen
2 Replies
2. Shell Programming and Scripting
Hello all,
I would be happy if any one could help me with a shell script that would determine all the processes running on a Unix server and post a mail if any of the process is not running or aborted.
Thanks in advance
Regards,
pradeep kulkarni.
:mad: (13 Replies)
Discussion started by: pradeepmacha
13 Replies
3. Shell Programming and Scripting
Hi guys,
I neet to run sqlldr to charge about 50,000 files every day to my DWH, so I need to make an script to keep about 100 processes of sqlldr running at the same time.
So, the issue is that i've been trying for a few days to make an script which can keep that amount of processes running, so... (2 Replies)
Discussion started by: razziel
2 Replies
4. UNIX for Dummies Questions & Answers
I am trying to see if a process is running what was its start time.
here is the code that I am using
if
then
echo 'Gateway output processing started.'
else
VAR=$(ps -ef | grep batch_output_x )
...
fi
now the problem i see is when the process is running i get two... (3 Replies)
Discussion started by: akabir77
3 Replies
5. UNIX for Dummies Questions & Answers
I have a script that executes a MAIN JAVA FILE
It does check if the process is already running or not by using this code
w_pid=`ps -efx | grep -v grep | grep "FileTransactionArchiveMain dvlp"|awk '{print $11}'`
if
then
#echo 'Another instance is running.'
exit
fi
Now I... (1 Reply)
Discussion started by: akabir77
1 Replies
6. Shell Programming and Scripting
Hi,
Do anybody experience to write a bash script in order to kill a specific process (java) after certain time of running?
eg.
java java.jar task_run.txt
I will run a java program (java.jar) which will run a long list of process (task_run.txt) one by one.
I plan to terminate the java... (5 Replies)
Discussion started by: perl_beginner
5 Replies
7. Shell Programming and Scripting
Frineds I need assistance in writing a script . Newbie to scripting.
How to find list of processes that are running more than an hour . Below i used the step to get the etime and stime . Now by getting the result i need to display longer time process with full listing.
ps -aef -o... (10 Replies)
Discussion started by: ajayram_arya
10 Replies
8. Shell Programming and Scripting
Need help in scripting . Below is the situation and need your inputs
Checking all the processes, scripts running time based on user input time . Below Example
ps -aef -o user,pid,etime,stime,args| grep sleep
<user> 28995 01:24 14:14:39 sleep 120
<user> 29385 00:52 14:15:10... (8 Replies)
Discussion started by: ajayram_arya
8 Replies
9. Shell Programming and Scripting
I use this command to get the time elapsed for a process
ps -eo pid,pcpu,pmem,user,args,etime,cmd --sort=start_time | grep perl
It gives in format
19990 0.0 0.0 user /usr/bin/php 5-09:58:51 /usr/bin/php
I need in seconds.
Please use CODE tags for sample input and output as well... (2 Replies)
Discussion started by: anil510
2 Replies
10. Shell Programming and Scripting
I am running a script which will read the data from fail line by line and call the Java program by providing the arguments from the each line.
The Java code is working fast for few records and for some records its getting hanged not providing response for morethan one hour.
Currently am... (4 Replies)
Discussion started by: dineshaila
4 Replies
CRON(8) System Manager's Manual CRON(8)
NAME
cron - daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-l load_avg] [-n]
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'. The -n option
changes this default behavior causing it to run in the foreground. This can be useful when starting it out of init.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d directory, which are in a different format (see crontab(5)). Cron then
wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut-
ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if
such exists).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if
time has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
PAM Access Control
On SUSE LINUX systems, crond now supports access control with PAM - see pam(8). A PAM configuration file for crond is installed in
/etc/pam.d/crond . crond loads the PAM environment from the pam_env module, but these can be overriden by settings in the crontab file.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files.
Naturally this is not relevant if cron was built to use syslog(3).
CAVEATS
In this version of cron, /etc/crontab must not be writable by any user other than root. No crontab files may be links, or linked to by any
other file. No crontab files may be executable, or be writable by any user other than their owner.
SEE ALSO
crontab(1), crontab(5), pam(8)
AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 10 January 1996" CRON(8)