Schedule Resource

The Schedule resource provides a means of automatically scheduling the connection of the Client to the Director. Each Director resource can have a different Schedule resource. No resource is required. If no is used, the Client will connect automatically to the Director at the startup.

The explanation on how to read the directive format:

  • Name: Contains the linked name of the directive.

  • Description: Explains what the directive does.

  • Value: Indicates what type of value to provide (e.g., <type-specification>).

  • Data Type: Specifies the type of data expected.

  • Values: Lists specific acceptable values.

  • Required: If present, indicates that the directive must be set by the user, there is no default value.

  • Default: If present, indicates that the directive has a predefined value that does not need to be set by the user, cannot be removed.

  • Comment: Additional important notes.

  • Example: Shows a usage example.

Schedule Start of the Schedule directives.

Name

Description: The name of the schedule being defined.

Value(s): <name>

Data Type: string

Required: Yes

Enabled

Description: This directive allows you to enable or disable the resource.

Value(s): <yes|no>

Data Type: boolean

Default: yes

Connect

Description: Defines when a Client should connect to a Director.

Value(s): <connect-overrides, date-time-specification>

Data Type:

Comment: You may specify multiple Connect directives within a resource. If you do, they will all be applied (i.e. multiple schedules). If you have two Connect directives that start at the same time, two connections will start at the same time (well, within one second of each other). It is not recommended to have multiple connections at the same time.

Connect-options are specified as: keyword=value where the keyword is MaxConnectTime and the value is as defined on the respective directive formats for the Job resource. You may specify multiple Connect-options on one directive by separating them with one or more spaces or by separating them with a trailing comma. For example:

MaxConnectTime=<time-spec> specifies how much time the connection will be attempt and active.

The Date-time-specification is similar to what exists for Job scheduling.

Go back to the File Daemon (Client) Resource Types page.

Go back to the Technical Reference for File Daemon.

Go back to the main Technical Reference page.