ScreenshotThis module implements a CRON daemon for use by administrators and other modules to periodically run jobs on the NAS. To simplify job management and to be more flexible this module uses a combination of CRON and Anacron to provide different ways to inject jobs.

Cron is a time-based job scheduler in Unix-like computer operating systems. Cron enables users to schedule jobs (commands or shell scripts) to run periodically at certain times or dates. It is commonly used to automate system maintenance or administration, though its general-purpose nature means that it can be used for other purposes

Supported Models

This module should work for the following models:

1U4200XXX, N2310, N2800, 1U4500, N4310, N4510U, 1U4600, N4510UPRO, M3800, N4800, N0503, N4800Eco, N2200XXX, N5550, N2520, N2560, N3200PRO, N6850, N3200XXX, N7510, N4100PRO, N7700PROv2, N4200, N8800PROv2, N4200Eco, N8900, N4200PRO, N8850, N4520, N8900V, N10850, N4560, N12000, N5200, N12000PRO, N5200PRO, N12000V, N5200XXX, N16000, N5500, N16000PRO, N7700, N16000V, N7700+, N7700PRO, N7700SAS, N8200XXX, N8800, N8800+, N8800PRO, N8800SAS


Extract the module binary package (.mod) from the archive and install it.

Note: If upgrading from a release prior to 1.01.01 please make a manual backup of the cron cronfiguration before uninstalling the old release.

Binary releases

cronie : 1.4.11 (from the Fedora Project)


After enabling the module the module status and configuration page can be accessed. This page allows to manage cron jobs and restart the cron daemon (crond) and to reset the configuration and jobs to their defaults.

Through the modules web interface administrators can create cron jobs using the usual crontab file format. Each line consists of 7 fields separated by spaces:

  1. minute
  2. hour
  3. day of month
  4. month
  5. day of week
  6. username
  7. command and arguments

The modules cron daemon supports the extended crontab format. A detailed documentation on the format is available on the module configuration page.

Module developers can maintain their own per module crontab files that follow the same syntax. These crontab file should be placed into the directory


by the modules start script. To make sure unique file names are used I would suggest to use a file name that starts with "module.MODULENAME" with MODULENAME replaced by the actual name of the module the cron job belongs to.

If no specific execution time is required a moduloe developer can simply place a script to be executed in either a hourly, daily, weekly or mothly basis into the appropriate directory of:


Changes to the crontab or script files are detected automatically. There is no need to restart or reload the daemon.

Starting with version 1.01.00 sending mails on cron execution is supported. This feature uses the mail notification settings of the NAS. There is no need to actually enable mail notifications - just the various settings are used. To send mail from crond just add


to the crontab file.

Known issues


Further informationen


[file] FaJoCron 1.02.00
MD5: 55b3a2909704db68d2aa9d8b40876d4b
313.74 KB
[file] FaJoCron 1.01.02
MD5: ed2888c4cbc6d75ce59fa829645d3157
255.96 KB