[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
howtos:general_admin:task_scheduling [2015/06/24 14:45 (UTC)] – tdrssbhowtos:general_admin:task_scheduling [2015/06/24 19:25 (UTC)] – tdrssb
Line 27: Line 27:
 job 4 at 2015-06-22 12:01  job 4 at 2015-06-22 12:01 
 darkstar:~%  darkstar:~% 
 +</code>
 +
 +=====File-driven at=====
 +Commands can also be contained within a file and run by **//at//**:
 +<code>
 +darkstar:~% at 12:32 -m -f /usr/local/bin/my_script.sh
 +warning: commands will be executed using (in order) a) $SHELL b) login shell c) /bin/sh
 +job 8 at 2015-06-22 12:10
 +</code>
 +The **-m** flag will email the user after completion of the command; the **-f** flag specifies the command will read the job from a file, not from standard input. After the command is typed in (and the appropriate warning is displayed), the **//at//** job number((As distinct from a process ID (PID) known to the operating system)) is displayed.
 +
 +=====at Internal Scheduling=====
 +The job numbers provided after a command is typed in, or when a file is read, allow the user to know which internal job will be run in sequential order. If a user wants to delete a specific task, all that needs to be known is this internal job number. To remove the job, the command **//atrm//** (**__at__ __r__e__m__ove**) is used:
 +
 +<code>
 +darkstar:~%  at -l
 +7      2015-06-22 12:10 p tux
 +8      2015-06-22 12:15 p root
 +</code>
 +
 +The command **//atq//** (**__at__ __q__ueue**) is the same as **//at -l//**:
 +
 +<code>
 +darkstar:~%  atq
 +7      2015-06-22 12:10 p tux
 +8      2015-06-22 12:15 p root
 +</code>
 +
 +To remove the user job, use **//atrm//** with the job number:
 +<code>
 +darkstar:~%  atrm 7
 </code> </code>
  
Line 53: Line 84:
 The //crontab// file syntax is: The //crontab// file syntax is:
  
-minute(0-59) hour(0-23) day(1-31) month(1-12) weekday(0-6) command+<code> 
 + # * * * * *  command to execute 
 + # │ │ │ │ │ 
 + # │ │ │ │ │ 
 + # │ │ │ │ └───── day of week (0 - 6) (Sun(0) /Mon (1)/Tue (2)/Wed (3)/Thu (4)/Fri (5)/Sat (6)) 
 + # │ │ │ └────────── month (1 - 12) 
 + # │ │ └─────────────── day of month (1 - 31) 
 + # │ └──────────────────── hour (0 - 23) 
 + # └───────────────────────── min (0 - 59) 
 +</code>
  
 Using an asterisk in any placeholder location, will match any value. For example, the following will run //example_script.sh// at noon (1200) everyday during the first three months of the year: Using an asterisk in any placeholder location, will match any value. For example, the following will run //example_script.sh// at noon (1200) everyday during the first three months of the year:
Line 86: Line 126:
   * Originally written by [[wiki:user:vharishankar | vharishankar]]   * Originally written by [[wiki:user:vharishankar | vharishankar]]
   * Contrbutions by [[wiki:user:mfillpot |mfillpot]], [[wiki:user:tdrssb |tdrssb]]   * Contrbutions by [[wiki:user:mfillpot |mfillpot]], [[wiki:user:tdrssb |tdrssb]]
 +  * Example crontab example modified from [[en.wikipedia.org/wiki/cron]]
 <!-- Please do not modify anything below, except adding new tags.--> <!-- Please do not modify anything below, except adding new tags.-->
 <!-- You must also remove the tag-word "template" below. Otherwise your page will not show up in the Table of Contents --> <!-- You must also remove the tag-word "template" below. Otherwise your page will not show up in the Table of Contents -->
 {{tag>howtos task_scheduling needs_attention author_vharishankar author_mfillpot}} {{tag>howtos task_scheduling needs_attention author_vharishankar author_mfillpot}}
  

Trace:

howtos:general_admin:task_scheduling ()