 |
you can work around this by scheduling monthly five minutes early and disallowing duplicate jobs. While I think you're right that we need something like "every friday, but the last", I would assume that priority in this context would override the job's priority (like pool and level do) and not declare the priority of this schedule entry. Can you update your proposal so we don't have this kind of ambiguity? |
|
|
The problem with the workaround is, that than one job is marked as canceled this is confusing the enduser (which is in our SME scenario is set up to control backups via webui). Explaining to the user that the job marked as canceled (failed) but it isn't, is not leading into the right directions how to handle failed jobs. Regarding priority I meant, that the schedule itselfs has priorities but not in the sense like priorities are handled on jobs but in the way that a schedule with a higher priority overrides the lower priority ones. For example having 5 schedules, scheduled at the same point in time, the one with highest priority wins. |
|
|
I totally understand you request and the drawbacks of the automatic cancelling. The main problem I have right now is, that the configuration syntax your propose is ambigous and misleading. If you can come up with something that isn't misleading, we might consider to put this on the agenda. |
|
|
Than maybe the best thing is to find another verb instead of priority, because with the implementation shown above there are really a lot things possible where more than one condition applies. For example (a litte bit overdriven but just to illustrate it clearly) you schedule a job on the 30th of the month, which may also be the last day in the month and allso a friday, having schedules for fridays, last day of the month in additiion to the schedule for 30th of the month, you could control which one should take precedence. Maybe "precendence" is also the word to be used :-) |
|
|
"rank" comes also to mind |
- Anonymous
