10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Dear Gurus,
I want to check if file got created in less than 10 hrs in .ksh.
Here is my requirement
In $var5 : I'm storing file name
In $var4 I have stored : select to_char(sysdate,'YYYYMMDDHH:MM:SS') from dual;
If that file date time is less than 10 hrs, then I need to check
if less... (1 Reply)
Discussion started by: thummi9090
1 Replies
2. Shell Programming and Scripting
Hi Friends,
Can anybody help me to create a perl script to generate log file for last 24 hrs from cron log file ??
Thank You (2 Replies)
Discussion started by: syamji.vm
2 Replies
3. Shell Programming and Scripting
I know you can supply the find command with an option to find files > than N days old. Is there some way to do this to find files that are > than N hours old.
I want to do somthing like this:
find . -mtime + (now - 2hrs) -print
If not is there a way to do this with sed or awk or some... (5 Replies)
Discussion started by: BeefStu
5 Replies
4. Shell Programming and Scripting
I have to retain only 1 day files in my system an I have to delete all the other files which are older than 24 hrs. Please let me know the option I have to give in the find -mtime command. (3 Replies)
Discussion started by: rajesh8s
3 Replies
5. Shell Programming and Scripting
hi all,
I need to find files in a directory which are older than N hrs...
n can be 1,2,3,.. etc
when tried using -mtime option it gives all the files in the last 24hrs from the current time .
please help me out on this ..
thanks (8 Replies)
Discussion started by: sparks
8 Replies
6. UNIX for Dummies Questions & Answers
I wanted to know what command should I use to see the files created in last 2 hours in a given directory.
I know to see the files changed in last one day I can use this:
find /admin//dump -type f -ctime -1 -print | xargs ls -lt|pg
However I am not getting what should I use if I wanted tol... (4 Replies)
Discussion started by: rsonakiya
4 Replies
7. Shell Programming and Scripting
Hi all,
I am trying to figure out a method to flag an error if a file has not arrived in a certain directory within 24 hrs of the last one arriving.
I am currently writing the time to a file when a file is recieved. I then want to check for a new file reguarly but flag an error if it has been... (3 Replies)
Discussion started by: pxy2d1
3 Replies
8. Shell Programming and Scripting
Hi
I am doing a process of converting all the values of key column into a row, for eg
Key col1 col2
1 1 1
1 2 1
1 1 3
1 3 1
2 ... (2 Replies)
Discussion started by: nvuradi
2 Replies
9. SuSE
I Have a SUSE Linux Enterprise server 9.0. When I start the server , using date command I daily find that the time it is showing is 00.00 Hrs. It shows the date correctly. Every day I have to set the time using the date command.
I am facing this proble from last 3 weeks but couldn't find a... (4 Replies)
Discussion started by: V.V.KUMAR
4 Replies
10. Shell Programming and Scripting
Hi gurus
I am currently using the below mentioned grep to find timestamp of last generated log file.
touch -t $time_search dummy
ecust_time_stamp=$(find . -name 'eCustomerCME*' -newer dummy -type f -exec ls -ltr {} \; | tail -1 | awk ' { print $6,$7,$8 } ')
I calculate... (3 Replies)
Discussion started by: ragha81
3 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)