Scheduling Tab
Previous Topic  Next Topic 


The Scheduling tab controls the time periods in which the application is allowed to run. It also controls regularly scheduled restarts of the application. The tab has two sections: Process Run and Restarts. Note that the scheduling defaults mean the service is run 24x7.



The settings in the Process Run section are used to restrict when the application can execute. FireDaemon Pro will not start the application unless all the time and date conditions in this section are satisfied.


Process Run Section


Field

Purpose

Start Time

This is the time at which the application will commence execution. If a start time is specified, the application will never be allowed to run before this time on any given day.

End Time

This is the time at which the application will halt execution. If an end time is specified, the application will never be allowed to run after this time on any given day.

Start From

This is the date on or after which the application may commence execution. If a start date is specified, the application will never be allowed to run on any day prior to this date.

Ending On

This is the date before or on which the application will halt execution. If an end date is specified, the application will never be allowed to run on any day after this date. Note: to run a process only for one day, set the start date to that day and the end date to the following day.  The service will not run on the day specified by the Ending On day.

Daily

These are the days of the week on which the application may run. By default, the application is allowed to run on any day of the week. If one or more days of the week are disabled, the application will never be allowed to run on those days. On a day that is enabled, the application will potentially be allowed to run, subject to the limitations of the start and end times, and start and end dates described above. Note that id the Start Time and End Time overlap a day boundry (eg. 11PM to 1AM) and if an ending day is not checked (eg. Tuesday) then the application will terminate at midnight (ie. 12PM on Monday).

Monthly

These are the days of the month on which the application may run. By default, the application is allowed to run on any day of the month. This may be restricted to a single day of the month, or to a range of days in the month, the range being inclusive. A range may be normal (e.g. from 10 to 12), or wrap-around (e.g. from 12 to 10).


If one or more days of the month are disabled, the application will never be allowed to run on those days. On a day that is enabled, the application will potentially be allowed to run, subject to the limitations of the start and end times, and start and end dates described above.


Restarts Section


The Restarts section is used to periodically force a running application to restart.


Field

Purpose

Schedule a Restart

This field specifies the frequency for the restart operation. A range of frequencies is available, varying from once per hour to once per month plus At specific time and User Defined. The restart occurs after the chosen interval has elapsed since the application commenced execution. For example, if a service is started at 03:45 on January 12th on a weekly restart schedule, it will be automatically restarted at 03:45 on Jan 19th, Jan 26th, Feb 2nd etc.

User Defined

This is the field to the right of Schedule a Restart. It is only active when Schedule a Restart is set to User Defined. When active the application can be restarted by the second. The minimum realistic value is 60 seconds (a smaller value can be set but is not recommended).

Restart Delay

If an application is to be automatically restarted, this field specifies the amount of time (in milliseconds) that FireDaemon Pro will pause before restarting the application.

Restart Time

If Schedule a Restart is set to At Specific time the service this is the time that the application will be restarted.


Where periodic restarts are enabled for an application, normal FireDaemon Pro processing will occur each time a restart is performed, e.g. graceful shutdown processing, pre-launch delay and pre- and post- service program execution.  The Flap Detection counter is not incremented during a scheduled restart operation.