Sponsored Content
Full Discussion: schedule a job without Cron
Top Forums Shell Programming and Scripting schedule a job without Cron Post 302599339 by pravin27 on Thursday 16th of February 2012 09:19:45 PM
Old 02-16-2012
schedule a job without Cron

Hi All,

Is there any way (any utility) to schedule a job to run once in a week on RedHat Linux ?

Note- Do not using Crontab.

Thanks
Pravin
 

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to Schedule job using cron(URGENT)

Hello All, I m newbie to Job scheduling. Suppose i have 2 files s1.sh and s2.sh i want to make a schedule such as run s1.sh at 2AM everyday and run s2.sh 9Pm everyday. Can anyone tell me how to schdule that using CRON and i want to know what is CRON and CRONTAB. Thanks in advance (2 Replies)
Discussion started by: ravi.sadani19
2 Replies

2. Shell Programming and Scripting

unable to schedule job in cron

Hi, from normal user(oracle) i am unable to run scheduled job in cron: os version: bash-2.03$ uname -a SunOS sumail02 5.8 Generic_117350-39 sun4u sparc SUNW,Ultra-60 bash-2.03$ crontab -l 55 * * * * sh /oracle/statistics.sh > /dev/null 2>&1 bash-2.03$ cat /oracle/statistics.sh... (2 Replies)
Discussion started by: prakash.gr
2 Replies

3. Shell Programming and Scripting

Cron to schedule job at different times

Hi, I want to run cron scheduler to run some script at different times of the day.But these times don't have some fix intervals. So how we can run jobs at 6:30AM, 1:00PM and 4:30PM everyday. Please help. Thanks Neeraj (2 Replies)
Discussion started by: apjneeraj
2 Replies

4. Shell Programming and Scripting

Schedule a Cron job

Hi all, I am new to cron jobs.. i wanted to schedule a cron job that wil send a mail to me at 3:00PM on 10th August ie is on Wednesday. 0 15 10 8 3 echo "message from UNIX here"|mail -s "your subject here" user@user.com However this was not executed... Can anyone please... (0 Replies)
Discussion started by: ch33ry
0 Replies

5. UNIX for Dummies Questions & Answers

Schedule a cron job

Hi, Can anyone help me out with scheduling a cron job for the below: i wnated to delete file from a folder on every sunday at 05:00 AM this is code i have used. ******************************************************* 0 05 * * 0 find /abc/xyz/pqrs/bak/ -type f -mtime +30 -exec rm -f... (5 Replies)
Discussion started by: ch33ry
5 Replies

6. UNIX for Beginners Questions & Answers

Schedule the cron job for every 21day on saturday

Please guide me how to schedule the cron job to run on every Saturday at 6am with the interval of 21 days. (2 Replies)
Discussion started by: raghavendrajsv
2 Replies

7. UNIX for Beginners Questions & Answers

Cron job is not running on schedule

Scheduled job is not running on time.but it is running when executing same command manually. 25 10 * * * /code/bin/ACCOUNT.ksh 1 >/dev/null 2 >&1 Manually executing the same Ksh -x /code/bin/ACCOUNT.ksh 1 >/dev/null 2 >&1 Followed steps Crontab -e Added the job to cron tab. (4 Replies)
Discussion started by: Myguest
4 Replies
job(n)								 Tnm Tcl Extension							    job(n)

__________________________________________________________________________________________________________________________________________________

NAME
job - Invoke Tcl procedures at regular intervals. _________________________________________________________________ DESCRIPTION
The job command provides a convenient mechanism to implement Tcl procedures that are invoked at regular intervals. Jobs are activated from the Tcl event loop. Every job can have arbitrary attributes to store job specific state information between two invocations. These attributes help to avoid global variables in order to keep the Tcl name-space clean. The job scheduler itself relies heavily on the Tcl timer interface which itself depends on the system clock. Moving the system clock back- wards can have the effect that jobs are not activated for the amount of time the system clock was moved backwards. Similarly, moving the system clock forward can have the effect that jobs are activated earlier for the amount of time the system clock was moved forward. JOB COMMAND
The job command allows to create new jobs and to wait for jobs to complete. The job command can also be used to retrieve status information from the job scheduler. job create [option value ...] The job create command creates a new job object. The options can be used to configure the behaviour of the new job. See the config- ure command below for the details. job current The job current command returns the name of the currently running job. An empty string is returned if no job is running. job info The job info command returns a list of all job names. The list will be empty if there are no jobs known in this Tcl interpreter. job schedule The job schedule command invoke the scheduler. This is usually done automatically from the event loop. This command may be used dur- ing long computations since the scheduler is not preemptive. Note, this command can cause arbitrary side effects and should be used with care. job wait The job wait command blocks until all existing jobs have been finished. The command will wait infinitely if there is at least one job left. Events are processed while waiting for the jobs to finish which can have arbitrary side effects. JOB INSTANCE COMMAND
Every job is represented by a job object command which allows to manipulate the job. job# attribute [name [value]] The job# attribute command allows to save job specific data in job attributes. If called without any arguments, all existing attribute names for this job will be returned. If called with a name argument, the current value of the attribute will be returned. Non-existing attributes do not produce an error. Instead, an empty string is returned. Calling the option with a name and a value causes the value to be saved in the job attribute. job# cget option The job# cget command returns the current value of a configuration option. See the description of supported options below. job# configure [option value ...] The job# configure command manipulates configuration options. See the description of supported options below. A list describing all current options is returns if the options argument is missing. job# destroy The job# destroy command destroys the job object. This command forces the object to change into the expired state. The scheduler will cleanup this object the next time it is active. job# wait The job# wait command blocks and processes events until the current job changes into the expired state. JOB OPTIONS
Every job has associated configuration options which control when a job is activated and which Tcl command is bound to the job. -command command The -command option defines the Tcl command that is evaluated whenever the job is activated. -interval time The -interval option defines the time interval between two job activations in milliseconds. -iterations number The -iterations option defines the total number of times that a job is activated. If this value reaches 0, the job will change its state to expired. Note, if the iterations options is never used, it will also have the value 0 but nothing special happens to the job object. -status state The -status option provides access to the current job state. A job is always in one of the states waiting, suspended, running and expired. A job in the expired state will be removed from the system once the scheduler gets activated again. Suspended jobs are not activated by the job scheduler. A suspended job can be resumed by changing its state to running. -time time The -time option returns the number of milliseconds until this job is activated the next time. This option is read-only. SEE ALSO
scotty(1), Tnm(n), Tcl(n) AUTHORS
Juergen Schoenwaelder <schoenw@cs.utwente.nl> Tnm job(n)
All times are GMT -4. The time now is 05:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy