[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
howtos:general_admin:task_scheduling [2015/06/24 19:21 (UTC)] tdrssbhowtos:general_admin:task_scheduling [2015/06/24 19:36 (UTC)] (current) tdrssb
Line 55: Line 55:
 </code> </code>
  
 +To remove the user job, use **//atrm//** with the job number: 
 +<code> 
 +darkstar:~%  atrm 7 
 +</code>
  
 =====Using cron===== =====Using cron=====
Line 109: Line 112:
 </note> </note>
  
- +**//anacron//** is unique from **//cron//** in the respect that it does not expect the operating system to be running continuously like a 24x7 server. If the time of execution passes while the system is turned off**//anacron//** executes the command automatically when the machine is turned back on. The reverse is **not** true for **//cron//** - if the computer is turned off during the time of scheduled execution, **//cron//** will not execute the job. Another key difference between **//anacron//** and **//cron//** is the minimum chronological "granularity" - **//anacron//** can only execute jobs by //day//, versus the ability of **//cron//** to execute by the //minute//Finally, **//anacron//** can __only__ be used by root, while **//cron//** can be used by root and normal users.
- +
-<note> +
-The links in red are to non-existent articles. +
- +
-If you are experienced with those toolsplease feel free to write the articles. +
-</note>+
  
 ====== Sources ====== ====== Sources ======
 howtos:general_admin:task_scheduling ()