[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 revisionBoth sides next revision
howtos:general_admin:task_scheduling [2015/06/24 18:44 (UTC)] tdrssbhowtos:general_admin:task_scheduling [2015/06/24 19:21 (UTC)] tdrssb
Line 28: Line 28:
 darkstar:~%  darkstar:~% 
 </code> </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>
 +
 +
  
 =====Using cron===== =====Using cron=====
 howtos:general_admin:task_scheduling ()