Cron - Revision history

imported>Cyounkins: link to systemd/timers

2023-02-03T03:42:43Z

link to systemd/timers

← Older revision		Revision as of 03:42, 3 February 2023
Line 2:		Line 2:
	==Deprecated==		==Deprecated==

	It is recommended to use systemd-timers. A few of many reasons:		It is recommended to use [[Systemd/Timers\|systemd-timers]]. A few of many reasons:
	* logs are logged to journalctl instead of relying on local mail		* logs are logged to journalctl instead of relying on local mail
	* different timers are independent of each other and do not share an environment		* different timers are independent of each other and do not share an environment

imported>SuperSandro2000: add deprecation notice

2023-01-02T17:30:24Z

add deprecation notice

← Older revision		Revision as of 17:30, 2 January 2023
Line 1:		Line 1:
	=~~Using~~ Cron=		=Cron=
			==Deprecated==

			It is recommended to use systemd-timers. A few of many reasons:
			* logs are logged to journalctl instead of relying on local mail
			* different timers are independent of each other and do not share an environment
			* better configurability like random offsets, run missed timers when machine was powered down and full systemd service option

	==General==		==General==

imported>Makefu at 14:50, 18 February 2018

2018-02-18T14:50:02Z

← Older revision		Revision as of 14:50, 18 February 2018
Line 21:		Line 21:

	<syntaxHighlight lang="nix">		<syntaxHighlight lang="nix">
	"/10 * * * johndoe . /etc/profile; ~~/run/current-system/sw~~/bin/r2e run"		"/10 * * * johndoe . /etc/profile; ${pkgs.rss2email}/bin/r2e run"
	</syntaxHighlight>		</syntaxHighlight>

Line 31:		Line 31:

	<syntaxHighlight lang="nix">		<syntaxHighlight lang="nix">
	"0 * * * * johndoe out=$( ~~/run/current-system/sw~~/bin/pass git pull 2>&1 ) \|\| echo $out"		"0 * * * * johndoe out=$( ${pkgs.pass}/bin/pass git pull 2>&1 ) \|\| echo $out"
	</syntaxHighlight>		</syntaxHighlight>

imported>Sjau at 13:38, 18 February 2018

2018-02-18T13:38:08Z

← Older revision		Revision as of 13:38, 18 February 2018
Line 31:		Line 31:

	<syntaxHighlight lang="nix">		<syntaxHighlight lang="nix">
	"0 * * * * ~~hyper~~ out=$( /run/current-system/sw/bin/pass git pull 2>&1 ) \|\| echo $out"		"0 * * * * johndoe out=$( /run/current-system/sw/bin/pass git pull 2>&1 ) \|\| echo $out"
	</syntaxHighlight>		</syntaxHighlight>

imported>Sjau at 13:37, 18 February 2018

2018-02-18T13:37:47Z

← Older revision		Revision as of 13:37, 18 February 2018
Line 25:		Line 25:

	The <code>. /etc/profile;</code> part first sources the profile file and hence loading the environment. After that, the actual command is being run in the proper environment. The above entry would run the rss2email program every <code>10 minutes</code> as user <code>johndoe</code>		The <code>. /etc/profile;</code> part first sources the profile file and hence loading the environment. After that, the actual command is being run in the proper environment. The above entry would run the rss2email program every <code>10 minutes</code> as user <code>johndoe</code>

			==Send mail only when error==

			In case you have set proper sendmail and defined a user where cron should send output to, you might want limit those emails only when cron encounters a problem. This can easily be achieved by storing the output of the command given into a variable and use the <code>\|\|</code> control operator to echo this output only when there is a non-zero exit status of the command.

			<syntaxHighlight lang="nix">
			"0 * * * * hyper out=$( /run/current-system/sw/bin/pass git pull 2>&1 ) \|\| echo $out"
			</syntaxHighlight>

	=See also=		=See also=

imported>Sjau: `is easier to spot that`


2018-02-17T20:21:52Z
<code> is easier to spot that <tt>

				
				
				
				
				
				← Older revision
				Revision as of 20:21, 17 February 2018
				
Line 2:
Line 2:
==General== ==General==



Cron is a very useful tool to run stuff at predefined times. Users, if allowed, can setup their own cron job, while the system crontab can be easily setup from the <tt>configuration.nix</tt> Cron is a very useful tool to run stuff at predefined times. Users, if allowed, can setup their own cron job, while the system crontab can be easily setup from the <code>configuration.nix</code>



<syntaxHighlight lang="nix"> <syntaxHighlight lang="nix">
Line 14:
Line 14:
</syntaxHighlight> </syntaxHighlight>



The above example would run the command <tt>date >> /tmp/cron.log</tt> as <tt>root</tt> user every <tt>5 minutes</tt> (indicated by <tt>*/5*</tt>. For more information regarding the cronjob entries, see the link below. The above example would run the command <code>date >> /tmp/cron.log</code> as <code>root</code> user every <code>5 minutes</code> (indicated by <code>*/5*</code>. For more information regarding the cronjob entries, see the link below.



==Loading environment== ==Loading environment==
Line 24:
Line 24:
</syntaxHighlight> </syntaxHighlight>



The <tt>. /etc/profile;</tt> part first sources the profile file and hence loading the environment. After that, the actual command is being run in the proper environment. The above entry would run the rss2email program every 10 minutes as user <tt>johndoe</tt> The <code>. /etc/profile;</code> part first sources the profile file and hence loading the environment. After that, the actual command is being run in the proper environment. The above entry would run the rss2email program every <code>10 minutes</code> as user <code>johndoe</code>



=See also= =See also=



imported>Sjau at 19:18, 17 February 2018
2018-02-17T19:18:38Z


				
				
				
				
				
				← Older revision
				Revision as of 19:18, 17 February 2018
				
Line 14:
Line 14:
</syntaxHighlight> </syntaxHighlight>



The above example would run the command <tt>date >> /tmp/cron.log</tt> as <tt>root</tt> user every <tt>5 minutes</tt> (indicated by <tt>*/5*</tt>. The above example would run the command <tt>date >> /tmp/cron.log</tt> as <tt>root</tt> user every <tt>5 minutes</tt> (indicated by <tt>*/5*</tt>. For more information regarding the cronjob entries, see the link below.



==Loading environment== ==Loading environment==
Line 25:
Line 25:



The <tt>. /etc/profile;</tt> part first sources the profile file and hence loading the environment. After that, the actual command is being run in the proper environment. The above entry would run the rss2email program every 10 minutes as user <tt>johndoe</tt> The <tt>. /etc/profile;</tt> part first sources the profile file and hence loading the environment. After that, the actual command is being run in the proper environment. The above entry would run the rss2email program every 10 minutes as user <tt>johndoe</tt>

=See also=
* [https://linux.die.net/man/5/crontab crontab(5): tables for driving cron]



[[Category:Configuration]] [[Category:Configuration]]





imported>Sjau at 18:57, 17 February 2018
2018-02-17T18:57:55Z


				
				
				
				
				
				← Older revision
				Revision as of 18:57, 17 February 2018
				
Line 15:
Line 15:



The above example would run the command <tt>date >> /tmp/cron.log</tt> as <tt>root</tt> user every <tt>5 minutes</tt> (indicated by <tt>*/5*</tt>. The above example would run the command <tt>date >> /tmp/cron.log</tt> as <tt>root</tt> user every <tt>5 minutes</tt> (indicated by <tt>*/5*</tt>.

==Loading environment==



However, sometimes cron won't run because it's missing the according environment (as it is the case for rss2email as example). In that case you just have to source the profile file first before running the desired command, like in the example below: However, sometimes cron won't run because it's missing the according environment (as it is the case for rss2email as example). In that case you just have to source the profile file first before running the desired command, like in the example below:





imported>Sjau: Created page with "=Using Cron= ==General==  Cron is a very useful tool to run stuff at predefined times. Users, if allowed, can setup their own cron job, while the system crontab can be easily..."
2018-02-17T18:57:30Z
Created page with "=Using Cron= ==General==  Cron is a very useful tool to run stuff at predefined times. Users, if allowed, can setup their own cron job, while the system crontab can be easily..."
New page
=Using Cron=

==General==



Cron is a very useful tool to run stuff at predefined times. Users, if allowed, can setup their own cron job, while the system crontab can be easily setup from the <tt>configuration.nix</tt>



<syntaxHighlight lang="nix">

  # Enable cron service

  services.cron = {

    enable = true;

    systemCronJobs = [

      "*/5 * * * *      root    date >> /tmp/cron.log"

    ];

  };

</syntaxHighlight>



The above example would run the command <tt>date >> /tmp/cron.log</tt> as <tt>root</tt> user every <tt>5 minutes</tt> (indicated by <tt>*/5*</tt>.



However, sometimes cron won't run because it's missing the according environment (as it is the case for rss2email as example). In that case you just have to source the profile file first before running the desired command, like in the example below:



<syntaxHighlight lang="nix">

      "*/10 * * * *   johndoe   . /etc/profile; /run/current-system/sw/bin/r2e run"

</syntaxHighlight>



The <tt>. /etc/profile;</tt> part first sources the profile file and hence loading the environment. After that, the actual command is being run in the proper environment. The above entry would run the rss2email program every 10 minutes as user <tt>johndoe</tt>



[[Category:Configuration]]

← Older revision		Revision as of 20:21, 17 February 2018
Line 2:		Line 2:
	==General==		==General==

	Cron is a very useful tool to run stuff at predefined times. Users, if allowed, can setup their own cron job, while the system crontab can be easily setup from the <tt>configuration.nix</tt>		Cron is a very useful tool to run stuff at predefined times. Users, if allowed, can setup their own cron job, while the system crontab can be easily setup from the <code>configuration.nix</code>

	<syntaxHighlight lang="nix">		<syntaxHighlight lang="nix">
Line 14:		Line 14:
	</syntaxHighlight>		</syntaxHighlight>

	The above example would run the command <tt>date >> /tmp/cron.log</tt> as <tt>root</tt> user every <tt>5 minutes</tt> (indicated by <tt>/5</tt>. For more information regarding the cronjob entries, see the link below.		The above example would run the command <code>date >> /tmp/cron.log</code> as <code>root</code> user every <code>5 minutes</code> (indicated by <code>/5</code>. For more information regarding the cronjob entries, see the link below.

	==Loading environment==		==Loading environment==
Line 24:		Line 24:
	</syntaxHighlight>		</syntaxHighlight>

	The <tt>. /etc/profile;</tt> part first sources the profile file and hence loading the environment. After that, the actual command is being run in the proper environment. The above entry would run the rss2email program every 10 minutes as user <tt>johndoe</tt>		The <code>. /etc/profile;</code> part first sources the profile file and hence loading the environment. After that, the actual command is being run in the proper environment. The above entry would run the rss2email program every <code>10 minutes</code> as user <code>johndoe</code>

	=See also=		=See also=

← Older revision		Revision as of 19:18, 17 February 2018
Line 14:		Line 14:
	</syntaxHighlight>		</syntaxHighlight>

	The above example would run the command <tt>date >> /tmp/cron.log</tt> as <tt>root</tt> user every <tt>5 minutes</tt> (indicated by <tt>/5</tt>.		The above example would run the command <tt>date >> /tmp/cron.log</tt> as <tt>root</tt> user every <tt>5 minutes</tt> (indicated by <tt>/5</tt>. For more information regarding the cronjob entries, see the link below.

	==Loading environment==		==Loading environment==
Line 25:		Line 25:

	The <tt>. /etc/profile;</tt> part first sources the profile file and hence loading the environment. After that, the actual command is being run in the proper environment. The above entry would run the rss2email program every 10 minutes as user <tt>johndoe</tt>		The <tt>. /etc/profile;</tt> part first sources the profile file and hence loading the environment. After that, the actual command is being run in the proper environment. The above entry would run the rss2email program every 10 minutes as user <tt>johndoe</tt>

			=See also=
			* [https://linux.die.net/man/5/crontab crontab(5): tables for driving cron]

	[[Category:Configuration]]		[[Category:Configuration]]

← Older revision		Revision as of 18:57, 17 February 2018
Line 15:		Line 15:

	The above example would run the command <tt>date >> /tmp/cron.log</tt> as <tt>root</tt> user every <tt>5 minutes</tt> (indicated by <tt>/5</tt>.		The above example would run the command <tt>date >> /tmp/cron.log</tt> as <tt>root</tt> user every <tt>5 minutes</tt> (indicated by <tt>/5</tt>.

			==Loading environment==

	However, sometimes cron won't run because it's missing the according environment (as it is the case for rss2email as example). In that case you just have to source the profile file first before running the desired command, like in the example below:		However, sometimes cron won't run because it's missing the according environment (as it is the case for rss2email as example). In that case you just have to source the profile file first before running the desired command, like in the example below:

Cron - Revision history

imported>Cyounkins: link to systemd/timers

imported>SuperSandro2000: add deprecation notice

imported>Makefu at 14:50, 18 February 2018

imported>Sjau at 13:38, 18 February 2018

imported>Sjau at 13:37, 18 February 2018

imported>Sjau: is easier to spot that

imported>Sjau at 19:18, 17 February 2018

imported>Sjau at 18:57, 17 February 2018

imported>Sjau: Created page with "=Using Cron= ==General== Cron is a very useful tool to run stuff at predefined times. Users, if allowed, can setup their own cron job, while the system crontab can be easily..."

imported>Sjau: `is easier to spot that`