![]() Of course, that's all "could this, could that" - I imagine most of that isn't done. and remount the drive and restore it's state before allowing any programs to resume. ![]() Since the OS has control of which programs can run when, logically it should be able to suspend all programs, flush the caches, unmount the drive. I assume there's a raft of things happen when the OS goes to sleep, I'd expect it to flush any cashes, notify all running programs, and so on. > be there start running again? Otherwise strange unexpected consequences may happen. > Depends on timings, really - will the remount happen before an programs which *might* expect that drive to If having that network connection removed/changed causes data loss, then that **IS** the fault of OS X (or rather the people that built it). If you are a portable device, and put into sleep mode, then it's unrealistic not to anticipate there being a high likelyhood of having the network removed/changed before you wake again. You might not be able to blame OS X for the network being unplugged, but you can blame it for not handling a reasonably forseeable event. > In any case, my issue was premature removal of network connection, which you can hardly blame OS X for (or any OS for that matter). Even if you don't unmount it, the system should be able to cope with a drive being physically disconnected and reconnected again while it's asleep. ![]() IMO it's obvious that when sleeping, you should unmount any drive (or at least any drive flagged as removable) which doesn't have open files on it. yes to flushing caches, however, it may not be entirely obvious which ones to try to un-mount - some drives you wouldn't want unmounting. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |