Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ISPConfig 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 551
    • Issues 551
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 42
    • Merge requests 42
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #1307

Closed
Open
Created Jan 03, 2011 by Simon Kurka@Bimon

cron options have to be handled differently

Hi,

I just noticed that the cron options are calculated like every other options when using Customer-Templates. I think they need an extra rule:

Now the min. delay between executions is added from each additional template, here the lowest value should be chosen. I can't really find out how the cron type is handled. It always switches to Full cron, although I set everything to URL cron.

These problems only appear using additional templates and not "custom" as Master-Template.

Sincerly, Simon Kurka

Assignee
Assign to
Time tracking