<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="https://knoppix.net/wiki3/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://knoppix.net/wiki3/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Polymath69</id>
		<title>Knoppix Documentation Wiki - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://knoppix.net/wiki3/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Polymath69"/>
		<link rel="alternate" type="text/html" href="https://knoppix.net/wiki/Special:Contributions/Polymath69"/>
		<updated>2026-09-17T03:17:37Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.23.3</generator>

	<entry>
		<id>https://knoppix.net/wiki/Crontab</id>
		<title>Crontab</title>
		<link rel="alternate" type="text/html" href="https://knoppix.net/wiki/Crontab"/>
				<updated>2009-09-06T11:20:52Z</updated>
		
		<summary type="html">&lt;p&gt;Polymath69: Cleared up some misconceptions and misinformations&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Scheduling jobs on [[linux]] requires two parts.  The first part is having the crond daemon running.  The second part is using the [[crontab]] command to create a schedule.  The schedule is a list of jobs with times that you'd like to have run.&lt;br /&gt;
&lt;br /&gt;
There are two versions of the command that you will use most of the time.&lt;br /&gt;
 &lt;br /&gt;
 crontab -e&lt;br /&gt;
To edit your crontab file.&lt;br /&gt;
 &lt;br /&gt;
 crontab -l&lt;br /&gt;
To list your crontab file.&lt;br /&gt;
 &lt;br /&gt;
 crontab -l &amp;gt; crontabbackup.txt&lt;br /&gt;
Another use of the -l switch allows you to send the schedule to a file.&lt;br /&gt;
&lt;br /&gt;
 crontab crontabbackup.txt&lt;br /&gt;
If you use the crontab -l option and send the output to a file as was shown in the prior command example, you can take that schedule and import it into another schedule.  All you have to do is use [[crontab]] and supply your backed up schedule file.  This is a great trick for [[knoppix]].  The creative use of this format of the command would be to import your schedule from a [[USB]] thumb drive or a hard drive partion.  You could even store the file on a MS Windows partition as long as the file is in [[linux]] format versus MS-DOS format.&lt;br /&gt;
 &lt;br /&gt;
 man 5 crontab&lt;br /&gt;
Use this man command to read about the formatting requirements for your '''crontab''' files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: there are two main types of crontab --&lt;br /&gt;
each user's crontab located in the directory /var/spool/cron/crontabs/''user'', and the main&lt;br /&gt;
system crontab '''/etc/crontab'''.&lt;br /&gt;
The '''crontab -e''' command will edit only the&lt;br /&gt;
per-user crontab files.  Use '''sudo vi /etc/crontab'''&lt;br /&gt;
to edit the systemwide crontab, but use this with&lt;br /&gt;
caution or as a last resort as this command will &lt;br /&gt;
bypass the syntax checking enforced by '''crontab -e'''.&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [http://www.math-linux.com/spip.php?article45  Crontab : Scheduling Tasks]&lt;br /&gt;
[[Category:Useful Linux Commands]]&lt;br /&gt;
&lt;br /&gt;
* [http://www.hxpi.com/cron_sandbox.php  A safe place to experiment with crontab commands is Cron Sandbox at HxPI where you can see straightaway a future schedule of run times for whatever crontab parameters you type in.]&lt;/div&gt;</summary>
		<author><name>Polymath69</name></author>	</entry>

	</feed>