cbj4074 Posted September 5, 2012 Report Share Posted September 5, 2012 Retrospect Multi-Server 9.0.2 (107) Mac OS X Server 10.6.8 Whenever I attempt to create a schedule or edit a schedule and I select "AM" from the AM/PM portion of the "start" time field, the "AM" value is not reflected in the Schedules pane above. In fact, if the AM/PM value is set to "AM", changing the time does not cause the time to change in the above pane, either. In other words, it seems that the "start" time field is "disabled" in some capacity whenever "AM" is selected therein. Quote Link to comment Share on other sites More sharing options...
twickland Posted September 5, 2012 Report Share Posted September 5, 2012 The earliest start date and time always needs to be in the future. If your first scheduled event is to happen on the day you are writing/editing the script, the execution time needs to be later than the time of the editing. If you want the script to regularly execute at an earlier time of day, you'll need to set your starting date later. The bug, such as it is, is that Retrospect does not supply an appropriate error message. The best solution, which many of us have suggested, is probably for Retrospect to accept the desired starting time but to automatically advance the starting date. Quote Link to comment Share on other sites More sharing options...
cbj4074 Posted September 5, 2012 Author Report Share Posted September 5, 2012 Thank you very much, twickland; that explanation makes sense. I will use the workaround, as described, until a proper fix is implemented. Quote Link to comment Share on other sites More sharing options...
bdunagan Posted December 14, 2012 Report Share Posted December 14, 2012 This issue (bug 3023) will be fixed in the next release. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.