Add items to crontab - Revision history

OneCD: layout changes and grammatical fixes.

2016-12-12T08:49:29Z

layout changes and grammatical fixes.

OneCD: general tidy-up and various grammatical fixes

2016-12-11T07:00:54Z

general tidy-up and various grammatical fixes

OneCD: linked SSH to 'How to SSH into your QNAP device'

2016-12-11T00:47:39Z

linked SSH to 'How to SSH into your QNAP device'

OneCD: included nano as an alternative text editor

2016-12-11T00:35:47Z

included nano as an alternative text editor

OneCD: added cron daemon restart

2016-12-06T20:42:51Z

added cron daemon restart

Freephile: Removes superflous methods, removes reference to telnet since I don't believe this is even possible through telnet

2016-07-27T17:21:16Z

Removes superflous methods, removes reference to telnet since I don't believe this is even possible through telnet

Fiskekroken: formatting

2016-03-06T11:27:52Z

formatting

Fiskekroken: Added full path to crontab (/usr/bin/crontab)

2016-03-06T11:25:12Z

Added full path to crontab (/usr/bin/crontab)

Fiskekroken at 11:16, 6 March 2016

2016-03-06T11:16:05Z

Show changes

Glenn: catchg

2015-10-26T10:15:25Z

catchg

@@ Line 9: / Line 9: @@
 === crontab ===
-The crontab can be used to execute tasks (scripts)&nbsp;based on a recurring schedule; by default the crontab is used, for example, to restart the webserver during the night.
+The crontab can be used to execute tasks (scripts)&nbsp;based on a recurring schedule. The crontab is used, for example, to restart the webserver during the night.
-To view the content of the crontab, login to your qnap using ssh and type:
+To view the content of your crontab, login to your QNAP via SSH and type:
 <pre>crontab -l
 </pre>
@@ Line 17: / Line 17: @@
 You will see a (small) list of crontab entries.
-== Stock crontab jobs ==
+This list is by no means complete. Jobs may depend on the firmware version, start times may vary. If you find a job on your QNAP, that is missing from the table, add it. The list could help to identify unwanted jobs that regularly wake up your harddisk(s).
 {| cellspacing="1" cellpadding="1" border="1" width="100%"
@@ Line 38: / Line 31: @@
 ! scope="col" | Explanation<br/>
 |-
-| 0 4 * * *
+| 0 4 * * *<br/>
 | /sbin/hwclock -s
 | [http://linux.die.net/man/8/hwclock http://linux.die.net/man/8/hwclock]<br/>
@@ Line 46: / Line 39: @@
 | vs_refresh is for share folder space usage calculation (for Network Share Management)<br/>
 |-
-| 0 3 * * 0
+| 0 3 * * 0<br/>
 | /etc/init.d/idmap.sh dump
 | related to SAMBA Active Directory configuration. Used if security is set to ADS.<br/>
 |-
-| 0 3 * * *
+| 0 3 * * *<br/>
 | /sbin/clean_reset_pwd
 | (unclear) might be the new behaviour of the network recycle bin (purging files after a certain amount of days)<br/>
 |-
-| 0-59/15 * * * *
+| 0-59/15 * * * *<br/>
 | /etc/init.d/nss2_dusg.sh
 | is a job of the Surveillance Station<br/>
@@ Line 96: / Line 89: @@
 Here are a couple of examples that append new entries to the crontab file:<pre>echo "1 4 * * * /share/custom/scripts/custom1.sh" >> /etc/config/crontab
 echo "40 5 * * * /share/custom/scripts/custom2.sh" >> /etc/config/crontab</pre>
 == Modifying entries ==
-You can edit the crontab file directly with your text editor:<br/><pre>vi /etc/config/crontab</pre>
 or
 <pre>nano /etc/config/crontab</pre>
 == Restart the daemon ==
@@ Line 107: / Line 111: @@
 When you're done, reload the crontab file and restart the cron daemon:
 <pre>crontab /etc/config/crontab && /etc/init.d/crond.sh restart</pre>
 == Notes ==
@@ Line 113: / Line 119: @@
 <pre>chmod +x filename.sh</pre>
-Tested on 3.6.0&nbsp;: works fine.&nbsp; Tested on 4.2.1 [[User:Freephile|Freephile]] ([[User_talk:Freephile|talk]]) 01:21, 28 July 2016 (CST)
-[[Category:Adding new services]]
+<div><span style="font-size:smaller">''These instructions have been tested on various versions of QNAP firmware from 3.6.0 onwards.''</span><br/></div> [[Category:Adding new services]]

@@ Line 93: / Line 93: @@
-== Adding/Changing cron entries ==
+== Adding entries at the command-line ==
-Edit <code>/etc/config/crontab</code> directly, then tell the cron service to reload the crontab. These changes will persist past a reboot. Like any changes to cron, you should test your script thoroughly before adding it.
+== Restart the daemon ==
-Here is an example which assumes you are ssh'd into your nas (as admin).
+When you're done, reload the crontab file and restart the cron daemon:
-<pre>echo "1 4 * * * /share/custom/scripts/custom1.sh" >> /etc/config/crontab
+<pre>crontab /etc/config/crontab && /etc/init.d/crond.sh restart</pre>
-Then reload crontab and restart cron daemon:
+== Notes ==
-PS. Don't forget to make your scripts executable! Otherwise they will silently fail! You tested your script, right?
+Don't forget to make your scripts executable! Otherwise they will silently fail! You tested your script, right?
 <pre>chmod +x filename.sh</pre>
 Tested on 3.6.0&nbsp;: works fine.&nbsp; Tested on 4.2.1 [[User:Freephile|Freephile]] ([[User_talk:Freephile|talk]]) 01:21, 28 July 2016 (CST)
 [[Category:Adding new services]]

@@ Line 5: / Line 5: @@
 === Skills required ===
-You must be able to connect to your QNAP device using [[SSH|SSH]] and edit using a text editor such as [[Using_vi|vi]] or nano.
+You must be able to connect to your QNAP device using [[How_to_SSH_into_your_QNAP_device|SSH]] and edit using a text editor such as [[Using_vi|vi]] or nano.
 === crontab ===

@@ Line 5: / Line 5: @@
 === Skills required ===
-You must be able to connect to your qnap using [[SSH|SSH]] and edit [[Using_vi|using vi]].
+You must be able to connect to your QNAP device using [[SSH|SSH]] and edit using a text editor such as [[Using_vi|vi]] or nano.
 === crontab ===

@@ Line 17: / Line 17: @@
 You will see a (small) list of crontab entries.
-<span style="color:red;">Do NOT edit the crontab in the usual way</span> Normally you can edit a user's crontab with
+<span style="color:red">Do NOT edit the crontab in the usual way</span> Normally you can edit a user's crontab with
 <pre>crontab -e</pre>
 However, due to the way the QNAP firmware updates crontab, it will be '''overwritten''' on the next reboot.
-Obviously you want your automation to survive reboots, so read the section below on how to modify and persist changes to cron on QNAP
+However, due to the way the QNAP firmware updates crontab, it will be '''overwritten''' on the next reboot. Obviously you want your automation to survive reboots, so read the section below on how to modify and persist changes to cron on QNAP
@@ Line 32: / Line 32: @@
 The following table is meant to bring some light into those built-in jobs.The list is by no means complete, jobs may depend on the firmware version, start times may vary. If you find a job on your QNAP, that is missing in the table, add it. The list could help to identify unwanted jobs on the QNAP&nbsp;that regularly wake up your harddisk(s).
-{| width="100%" cellspacing="1" cellpadding="1" border="1"
+{| cellspacing="1" cellpadding="1" border="1" width="100%"
 |-
 ! scope="col" | Default Time<br/>
@@ Line 99: / Line 99: @@
 Here is an example which assumes you are ssh'd into your nas (as admin).
 <pre>echo "1 4 * * * /share/custom/scripts/custom1.sh" >> /etc/config/crontab
-echo "40 5 * * * /share/custom/scripts/custom2.sh" >> /etc/config/crontab
+echo "40 5 * * * /share/custom/scripts/custom2.sh" >> /etc/config/crontab</pre>
 crontab /etc/config/crontab</pre>
 PS. Don't forget to make your scripts executable! Otherwise they will silently fail! You tested your script, right?
 <pre>chmod +x filename.sh</pre>
-Tested on 3.6.0&nbsp;: works fine.&nbsp; Tested on 4.2.1 [[User:Freephile|Freephile]] ([[User talk:Freephile|talk]]) 01:21, 28 July 2016 (CST)
+Tested on 3.6.0&nbsp;: works fine.&nbsp; Tested on 4.2.1 [[User:Freephile|Freephile]] ([[User_talk:Freephile|talk]]) 01:21, 28 July 2016 (CST)
 [[Category:Adding new services]]

@@ Line 146: / Line 146: @@
 Don't bother with that kind of script at all. Whenever you add a custom entry then follow this procedure
-<blockquote>1. Edit /etc/config/crontab and add your custom entry.<br/>2. Run '/<span style="line-height: 1.6;">usr/bin/crontab /etc/config/crontab' to load the changes.</span></blockquote><blockquote>3. Restart cron, i.e. '/etc/init.d/crond.sh restart'</blockquote>
+<blockquote>1. Edit /etc/config/crontab and add your custom entry.<br/>2. Run '/usr/bin/crontab /etc/config/crontab' to load the changes.&nbsp;<br/>3. Restart cron, i.e. '/etc/init.d/crond.sh restart'<br/></blockquote>
 If you follow this procedure then the changes survive a reboot (even a firmware upgrade), i.e. no need for any script to restore them.

← Older revision		Revision as of 10:15, 26 October 2015
Line 148:		Line 148:
	Tested on 3.6.0 : works fine.		Tested on 3.6.0 : works fine.

−	[[Category:~~Miscellaneous~~]]	+	[[Category:Adding new services]]