How to write a cron job for only 10 days? - unix

I need to write a cron job that runs daily, but for only 10 days and stops after
executing for 10 days.
As soon as I write a job, it should start and run for 10 days daily.


Do: 0 10 5-15 1 * command
for more information on crontab visit


As soon as you finished with the script, save to particular path. After that set a cronjob for that job.
Eg:
filename : /home/script/Job1
set cron:
* 00 10-20 * * /home/script/Job1
If suppose you are writing you job on 10th, then another 10 days it will run as my crontab at 12.00 A.M.

Related

Airflow pipeline doesn't run on scheduled time

I am trying to run a pipeline on say 'first Monday of the month'. My schedule interval is '30 17 * * 1#1' and start date is '2022-01-01' but it doesn't run. Any pointers on why it doesn't run on the scheduled time? Thank You

Airflow runs are skipped when we have more number of dag files

I have installed apache-airflow==1.10.8. I have around 200 dag files inside AIRFLOW_HOME folder. Each dag files may take an execution time of around 20 seconds. I have scheduled each dag file to run at every 2 minutes ' */2 * * * *'
. But when i see the logs of any particular dag, i see that dags are not executed for every 2 minutes. Attached the executed times that i got from the logs directory for a particular dag.
2020-06-02T10:14:00+00:00
2020-06-02T10:24:00+00:00
2020-06-02T10:34:00+00:00
2020-06-02T10:44:00+00:00
2020-06-02T11:14:00+00:00
2020-06-02T11:24:00+00:00
Following are the configurations in airflow.cfg
LocalExecutor ,
parallelism = 32
dag_concurrency = 16
max_active_runs_per_dag = 16
dagbag_import_timeout = 30
dag_file_processor_timeout = 50
task_runner = StandardTaskRunner
How can i make the airflow to execute the dags at every 2 minutes?
Additional details: Ubuntu 18.04 and Python 3.7

how oozie timezone work, it does not pick the right timezone?

I have oozie job running on CDH cluster. I have the following coordinator
<coordinator-app name="name" frequency="0 */5 * * *" start="2020-03-05T16:00Z" end="2020-03-07T16:00Z" timezone="America/New_York" xmlns="uri:oozie:coordinator:0.4">
I submitted this job at 15:15 new york time and oozie started the first job right away and it was marked at 15:00 (new york time) and the next one is scheduled for 19:00. I don't understand the time zone for oozie. Why it does not pick up the time zone I have specified ?

You can over-ride the Timezone when submitting the oozie job on the terminal
-timezone EST -config coordinator.properties -run

Asterisk call file

Good day. The call file details are
Channel: SIP/voipswitch/971556710034
MaxRetries: 6
RetryTime: 20
WaitTime: 30
Context: default
Extension: 971556710034
Priority: 1
with this setting I can connect call on my phone. Once call get received asterisk delete this file and stop calling. But I want to call on my phone after every 30 min and will receive every time.
Can some one please help to do this.

Put this line in /etc/crontab
*/30 * * * * asterisk cp /path/to/call/file /var/spool/asterisk/outgoing
This will copy call file to asterisk outgoing directory every 30 min.
Don't forget to restart crontab service.
service crontab restart

How to schedule a job every 10 mins using JIL script

How can I set a job in autosys which will run evening from 4pm to 5pm every 10 minutes?
Please help me how I can specify then start time parameter. I am new to this JIL script.
Also where can I get the complete details about scheduling a job using JIL script?

You can give the attribute start_mins for every 10 mins with the run_window. You can schedule jobs for every minute but you do not have it in seconds.
date_conditions: 1
days_of_week: all
start_mins: 00,10,20,30,40,50
run_window: "16:00-17:00"
timezone: india

/* ----------------- template ----------------- */
insert_job: template job_type: c
box_name: box1
command: <xxx>
machine: <hostname>
owner: <username>
permission: gx,ge
date_conditions: 1
days_of_week: all
start_mins: 0,30
run_window: "16:00-17:00
please refer to the cheatsheet for further details
http://supportconnectw.ca.com/public/autosys/infodocs/autosys_cheatsheet.asp

Use start_mins: "00,10,20,30,40,50"

Resources