 |
 |
What determines which updates require restarts?
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
Why is it that this current security update of Quicktime doesn't require a restart, when so many other OS X updates (including Quicktime) do?
I've always found this unusual, since under most Unix OSes restarts for updates are not required except for kernel changes. However, this particularly security update has really piqued my curiosity...
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Oct 2001
Location: San Diego, CA, USA
Status:
Offline
|
|
I think if it patches the kernel or a system library, it requires a restart (since it would be too difficult for the average user to bring their system back into a consistent state without restarting). I suspect this is a patch for QuickTime for Java, so fix the "Safari exploit."
|
|
Chuck
___
"Instead of either 'multi-talented' or 'multitalented' use 'bisexual'."
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status:
Offline
|
|
Security Updates always require restarts. And any critical component like a system framework will.
|
"The natural progress of things is for liberty to yield and government to gain ground." TJ
|
| |
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Aug 2004
Location: FFM
Status:
Offline
|
|
Originally Posted by Big Mac 
Security Updates always require restarts.
Well, this one doesn't.
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
Originally Posted by Big Mac
Security Updates always require restarts. And any critical component like a system framework will.
Why should it?
|
|
|
| |
|
|
|
|
|
|
|
Professional Poster
Join Date: Jun 2001
Location: Northwest Ohio
Status:
Offline
|
|
Originally Posted by besson3c
Why should it?
Because the Software Update application can never know exactly what applications or resources are in use at the time the updater is run. It is easier to tell the user to reboot than to have the installer quit all applications, log the user out and back in, etc. Not to mention that even doing that may not fix everything. Rebooting the system ensures that any old version of a component or framework is not still in the system and makes sure the system is consistent.
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
Originally Posted by Person Man
Because the Software Update application can never know exactly what applications or resources are in use at the time the updater is run. It is easier to tell the user to reboot than to have the installer quit all applications, log the user out and back in, etc. Not to mention that even doing that may not fix everything. Rebooting the system ensures that any old version of a component or framework is not still in the system and makes sure the system is consistent.
It is pretty easy to do an lsof to determine what libraries are in use at any given time, and if any are being updated by Software Update, notify the user, offer to restart services or apps, whatever.
I think that Apple should at least give users the option to not restart the computer. Even if Quartz/Aqua needs to be reloaded, this should be possible without restarting the entire OS. This just isn't really necessary. Am I missing something?
If Apple really wants OS X Server to succeed in mission critical environments, they should at least work on getting this to work in OS X Server.
(Last edited by besson3c; May 29, 2007 at 08:22 PM.
)
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
