Scheduler task options

When the Scheduler is enabled, each named  known to the Scheduler may be explicitly enabled or disabled via the task&#x27;s own    option (but typically the task&#x27;s   value defaults appropriately based on which  Messaging Server components are enabled), and if enabled (whether implicitly or explicitly) will be executed at the schedule set  via the   option for that task; e.g., msconfig&#x3e; show schedule.enable role.schedule.enable = 1 msconfig&#x3e; show mta.enable role.mta.enable = 1 msconfig&#x3e; show schedule.task:return_job.&#x2a; role.schedule.task:return_job.crontab = 30 0 &#x2a; &#x2a; &#x2a; lib/return_job The Scheduler supports the following named s in particular:



 , the Message Store&#x27;s message expiration job, that deletes from disk messages that users have deleted from their mailboxes, and purges messages from users&#x27; mailboxes according to administrative criteria, 

 , checking whether Messaging Server components such as server processes are available ("up") and responsive, 

 , the MTA&#x27;s log file purge job, that purges older MTA log files, 

 , the MTA&#x27;s message return job (message bouncer job), that returns (bounces) excessively old, undelivered messages, 

 , the Message Store&#x27;s database "snapshot" job, that captures a current-moment "snapshot" of the messages in the Message Store, 

 , the Message Store&#x27;s database "snapshot verification" job, that verifies whether snapshots are sound. 



Individual Scheduler tasks can themselves be enabled or disabled through the use of the  task option. For example, the following commands disable msprobe and explicitly enable imexpire: msconfig&#x3e; set schedule.task:msprobe.enable 0 msconfig# set schedule.task:expire.enable 1 Almost all Scheduler settings are refreshable: New tasks can be added, task parameters can be changed, disabled tasks can be enabled, and as of Messaging Server 8.0.1.2, enabled tasks can be enabled. In all of these cases a  will cause the changes to take effect.

At present only the outright deletion of a task requires a Scheduler restart: stop-msg sched start-msg sched Other tasks can be executed by the Scheduler. For instance, rather than executing the Message Store&#x27;s  job as a daemon as normally configured when   is enabled, a site can disable that daemon via   and instead configure the Scheduler to run the   command periodically.

See also:
 * enable Option
 * crontab Option
 * expire task options
 * msprobe task options
 * purge task options
 * return_job options
 * snapshot task options
 * snapshotverify task options
 * Scheduler options