Jump to content

Annoying shutdown and scheduled run behavior


Recommended Posts

I have 2 questions about how 5.0 behaves on OS X compared to OS 9. I suppose these are really complaints, not questions -- I guess what I would like is an explanation, and ideally a change in the next version <g>.

 

1. When Retrospect finishes a scheduled operation in OS X, it emits a warning beep and shuts down the Mac -- wham! -- just like that. A user on that Mac is given no opportunity to save open files in other applications. Under OS 9 it displayed the customary shutdown warning and applications on the Mac waited for open files to be saved before quitting. I assume this has to do with the default behavior of the OS, but it is not user-friendly.

 

2. When the Mac is asleep under OS X, Retrospect will not launch to execute a scheduled operation. Again, this compares unfavorably to its behavior under OS 9. Obviously, if the machine is unattended, it is very likely to go into sleep mode -- this is precisely why you set up scheduled operations. The behavior under OS X encourages energy waste by forcing the operator to disable sleep settings. I note that a similar situation exists for the client.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...