Sponsored Content
Full Discussion: crontab entry
Operating Systems AIX crontab entry Post 302291910 by Padow on Thursday 26th of February 2009 02:40:08 PM
Old 02-26-2009
Only business days?

You will need a real job scheduler for that. Autosys, BMC, etc. I don't know of any freeware job schedulers. if anyone does, please post!
Padow
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

crontab entry

hi all how to schedule a cron job running on last day of every third month at 12 midnight will the following work 0 0 30,31 3,6,9,12 * <required file> thanks (3 Replies)
Discussion started by: matrixmadhan
3 Replies

2. Shell Programming and Scripting

Crontab entry

Hello, I am trying to schedule a job to run every 15 minutes from 7am to 5:30pm. Could someone show me the syntax for this? Thanks. (1 Reply)
Discussion started by: bestbuyernc
1 Replies

3. UNIX for Advanced & Expert Users

crontab entry

Sometimes cron really upsets me and I cant figure out these types of wierd dates, but how do I get cron to run something on every other sunday? I am running Solaris 8. -S (4 Replies)
Discussion started by: Sowser
4 Replies

4. Shell Programming and Scripting

Crontab Entry

Hi Everyone , have a nice day given below is the line i have added in crontab * * * * * /Rauf/script2.sh intended to run this script after every minute , when i run this script manually it runs fine and produces output , but after adding it to crontab ( like given above ) , it doesnt work ... (5 Replies)
Discussion started by: Dastard
5 Replies

5. Solaris

crontab entry

How to set the crontab entry for every other Friday? Regards, Raj (1 Reply)
Discussion started by: rajip23
1 Replies

6. Solaris

crontab entry

Hi, i need to setup a cronjob that has will execute iostat command from morning to evening time. for instance the timing has will be like this. 8:00 A.M -- 6:00P.M how to define this entry in crontab Regards (3 Replies)
Discussion started by: jaweedak
3 Replies

7. UNIX for Dummies Questions & Answers

Crontab entry

What should be the crontab entry for a script: to run at 3:00 AM EST Sun, Mon, Tue, Wed, Thu, Fri (3 Replies)
Discussion started by: proactiveaditya
3 Replies

8. Solaris

crontab entry

hi i am new in solaris. i am accessing server through putty. i could not add entry in crontab. i have given "crontab -e" for add a new entry. It is not coming. what parameter i have to set for getting crontab -e thanks (1 Reply)
Discussion started by: sunnybee
1 Replies

9. UNIX for Dummies Questions & Answers

Crontab entry

Is this the correct entry to touch a file on 6/6 5AM? 00 05 06 06 * touch /support/home/.no_copy Please use next time code tags for your code and data (5 Replies)
Discussion started by: Me XMan
5 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 08:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy