Using the PRIORITY Keyword

There may be situations where there is a conflict between two TIMESPECs that cover the same path. In these cases you can define the priority of a TIMESPEC using the following syntax.

normal_timespec_syntax PRIORITY integer

normal_timespec_syntax is a legal TIMESPEC and integer represents the priority (the smaller the number, the higher the priority). The number can be positive, negative, or zero, and the value only has meaning when compared with other PRIORITY values.

Note: The PRIORITY keyword cannot be used with the MAXDELAY, or MAXSKEW constraint.