Kevin M. White
Kevin M. White
I would have to see the full super.log of a device that is affected. However, if you want the MOST consistent behavior then use `--schedule-zero-date-release` and then adjust your deadlines...
I rewrote a lot of that code can you please test with the latest version of `super`... https://github.com/Macjutsu/super/releases/tag/v5.1.0-rc1?
That last miniute is inclusive, but there should be an option to not have to define a time for allowing the full day.
This is partially implemented via the new scheduled installation options in https://github.com/Macjutsu/super/releases/tag/v5.0.0-beta2 Stay tuned...
This is now fully implemented in the latest build of `super` with the new `--schedule-workflow-active` option! https://github.com/Macjutsu/super/releases/tag/v5.0.0-beta3
Sorry for the delayed response, the `super` preference framework will be getting a significant rearchitecting in the 5.2 timeframe that will address the behavior.
Please check out the latest builds of `super`. I completley rewrote the preference mechanism to support more complicated workflows. In doing so the local settings file no longer caches changes...
Thanks for finding this... turns out there is also some acual `super` code that needs to be fixed as well.
Indeed... `super` started up and saw that no one was logged in... and then procededed to install. This would need to be a new feature to NOT do that since...
No plans to move to an agent b/c that could cause a cascade of issues. That being said, I do plan to implement features that allows for control of `super`'s...