on 4-10-2009 3:24 PM Lanny Marcus spake the following:
> On Thu, Apr 9, 2009 at 10:55 PM, D Tucny wrote:
>> 2009/4/10 Mike A. Harris
>>> Jerry Geis wrote:
What is the rule of thumb for reboots after updates...
>>> I'd say the rule of thumb is to do whatever works best for you, and that
>>> y
On Thu, Apr 9, 2009 at 10:55 PM, D Tucny wrote:
> 2009/4/10 Mike A. Harris
>> Jerry Geis wrote:
>> > What is the rule of thumb for reboots after updates...
>>
>> I'd say the rule of thumb is to do whatever works best for you, and that
>> you'll likely get quite the variety of different responses.
2009/4/10 Mike A. Harris
> Jerry Geis wrote:
> > What is the rule of thumb for reboots after updates...
>
> I'd say the rule of thumb is to do whatever works best for you, and that
> you'll likely get quite the variety of different responses. ;o)
>
> > Certainly if I update from 5.2 to 5.3 I reb
Mike A. Harris wrote:
> Jerry Geis wrote:
>> What is the rule of thumb for reboots after updates...
>
> I'd say the rule of thumb is to do whatever works best for you, and that
> you'll likely get quite the variety of different responses. ;o)
>
>> Certainly if I update from 5.2 to 5.3 I reboot.
Jerry Geis wrote:
> What is the rule of thumb for reboots after updates...
I'd say the rule of thumb is to do whatever works best for you, and that
you'll likely get quite the variety of different responses. ;o)
> Certainly if I update from 5.2 to 5.3 I reboot.
>
> But if you update something
Les Mikesell wrote:
>
> And in one case, I got kicked off of my ssh connection in mid-update.
> I'm still not sure what happened there but I had to install yum-utils
> and run yum-recover-transaction to continue.
>
That's why I use screen for remote updates.
__
Brian Mathis wrote:
> On Thu, Apr 9, 2009 at 2:10 PM, Les Mikesell wrote:
>> I had done the --downloadonly - and the disconnect wasn't network
>> related as other connections to the same site stayed up. It seemed like
>> something in the cleanup pass killed sshd - and the running yum, leaving
>>
On Thu, Apr 9, 2009 at 2:10 PM, Les Mikesell wrote:
> I had done the --downloadonly - and the disconnect wasn't network
> related as other connections to the same site stayed up. It seemed like
> something in the cleanup pass killed sshd - and the running yum, leaving
> a mess. The transaction r
Scott Silva wrote:
>
>>
>> And in one case, I got kicked off of my ssh connection in mid-update.
>> I'm still not sure what happened there but I had to install yum-utils
>> and run yum-recover-transaction to continue.
>>
> I always run my updates through screen. That way disconnects aren't a prob
on 4-9-2009 10:07 AM Les Mikesell spake the following:
> Scott Silva wrote:
> You only *really* need to reboot if/when you update the kernel. Yum/RPM
> takes care of restarting daemons, etc. during the update process. This
> is NOT MS-Windows
Yes, but any program that is alrea
Les Mikesell schrieb:
>
> You have some chance of 'knowing' the server side of things - a lot less
> about what other users might be running. What should you expect if you
> have logged in users over freenx, remote X or at the console running
> (say) firefox through an update? Or other long ru
Scott Silva wrote:
>
You only *really* need to reboot if/when you update the kernel. Yum/RPM
takes care of restarting daemons, etc. during the update process. This
is NOT MS-Windows
>>> Yes, but any program that is already running will keep using the old
>>> versions of the pr
on 4-9-2009 9:01 AM Robert Heller spake the following:
> At Thu, 09 Apr 2009 10:38:08 -0500 CentOS mailing list
> wrote:
>
>> Robert Heller wrote:
>>> At Thu, 09 Apr 2009 07:49:30 -0400 CentOS mailing list
>>> wrote:
>>>
What is the rule of thumb for reboots after updates...
Cer
At Thu, 09 Apr 2009 10:38:08 -0500 CentOS mailing list
wrote:
>
> Robert Heller wrote:
> > At Thu, 09 Apr 2009 07:49:30 -0400 CentOS mailing list
> > wrote:
> >
> >> What is the rule of thumb for reboots after updates...
> >>
> >> Certainly if I update from 5.2 to 5.3 I reboot.
> >>
> >> But
Robert Heller wrote:
> At Thu, 09 Apr 2009 07:49:30 -0400 CentOS mailing list
> wrote:
>
>> What is the rule of thumb for reboots after updates...
>>
>> Certainly if I update from 5.2 to 5.3 I reboot.
>>
>> But if you update something like krb5 or pam
>> does that require a reboot? Does the "fix
At Thu, 09 Apr 2009 07:49:30 -0400 CentOS mailing list
wrote:
>
> What is the rule of thumb for reboots after updates...
>
> Certainly if I update from 5.2 to 5.3 I reboot.
>
> But if you update something like krb5 or pam
> does that require a reboot? Does the "fix" get automatically loaded a
Warren, thank you very much for the info! I learned a lot.
On 4/9/09, Warren Young wrote:
> nate wrote:
>> Jerry Geis wrote:
>>> What is the rule of thumb for reboots after updates...
>>
>> only with new kernels.
>
> ...and then only when you want what the new kernel provides.
>
> I have my syste
On Thursday 09 April 2009, nate wrote:
> Jerry Geis wrote:
> > What is the rule of thumb for reboots after updates...
> >
> > Certainly if I update from 5.2 to 5.3 I reboot.
> >
> > But if you update something like krb5 or pam
> > does that require a reboot? Does the "fix" get automatically loaded
nate wrote:
> Jerry Geis wrote:
>> What is the rule of thumb for reboots after updates...
>
> only with new kernels.
...and then only when you want what the new kernel provides.
I have my systems configured so yum is allowed to download and install
new kernels, but don't usually reboot unless
Jerry Geis wrote:
> What is the rule of thumb for reboots after updates...
>
> Certainly if I update from 5.2 to 5.3 I reboot.
>
> But if you update something like krb5 or pam
> does that require a reboot? Does the "fix" get automatically loaded and used
> or do you just do a reboot always?
only w
What is the rule of thumb for reboots after updates...
Certainly if I update from 5.2 to 5.3 I reboot.
But if you update something like krb5 or pam
does that require a reboot? Does the "fix" get automatically loaded and used
or do you just do a reboot always?
Thanks,
Jerry
_
21 matches
Mail list logo
