See this announce mail here:
https://lists.centos.org/pipermail/centos-announce/2015-December/021518.html
Since it butchered the links, you can get ISOs here:
http://isoredirect.centos.org/centos/7/isos/x86_64/
You can upgrade with 'yum update'
Release notes here:
http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7
Enjoy, Johnny Hughes
On Dec 14, 2015, at 9:37 AM, Johnny Hughes johnny@centos.org wrote:
See this announce mail here:
https://lists.centos.org/pipermail/centos-announce/2015-December/021518.html
<snip>
I just updated to 7.2 from 7.1. I did lsb_release -a and it says 7.2.1511. I haven’t rebooted yet, which items would run with new binaries, anything that isn’t running yet? Ssay I had apache running, it wouldn’t pick up new apache until a reboot, right?
Thanks,
-wes
On 12/14/2015 05:46 PM, Wes James wrote:
On Dec 14, 2015, at 9:37 AM, Johnny Hughes johnny@centos.org wrote:
See this announce mail here:
https://lists.centos.org/pipermail/centos-announce/2015-December/021518.html
<snip>
I just updated to 7.2 from 7.1. I did lsb_release -a and it says 7.2.1511. I haven’t rebooted yet, which items would run with new binaries, anything that isn’t running yet? Ssay I had apache running, it wouldn’t pick up new apache until a reboot, right?
I have no idea, but there are security kernel updates:
https://lists.centos.org/pipermail/centos-cr-announce/2015-November/002347.h...
https://lists.centos.org/pipermail/centos-cr-announce/2015-December/002732.h...
And those will not be active without a reboot.
On Dec 14, 2015, at 4:57 PM, Johnny Hughes johnny@centos.org wrote:
On 12/14/2015 05:46 PM, Wes James wrote:
On Dec 14, 2015, at 9:37 AM, Johnny Hughes johnny@centos.org wrote:
See this announce mail here:
https://lists.centos.org/pipermail/centos-announce/2015-December/021518.html
<snip>
I just updated to 7.2 from 7.1. I did lsb_release -a and it says 7.2.1511. I haven’t rebooted yet, which items would run with new binaries, anything that isn’t running yet? Ssay I had apache running, it wouldn’t pick up new apache until a reboot, right?
I have no idea, but there are security kernel updates:
https://lists.centos.org/pipermail/centos-cr-announce/2015-November/002347.h... https://lists.centos.org/pipermail/centos-cr-announce/2015-November/002347.html
https://lists.centos.org/pipermail/centos-cr-announce/2015-December/002732.h... https://lists.centos.org/pipermail/centos-cr-announce/2015-December/002732.html
And those will not be active without a reboot.
Thanks to you and John R Pierce for your replies.
-wes
Date: Monday, December 14, 2015 20:38:23 -0700 From: Wes James comptekki@me.com
On Dec 14, 2015, at 4:57 PM, Johnny Hughes johnny@centos.org wrote:
On 12/14/2015 05:46 PM, Wes James wrote:
On Dec 14, 2015, at 9:37 AM, Johnny Hughes johnny@centos.org wrote:
See this announce mail here:
https://lists.centos.org/pipermail/centos-announce/2015-Decembe r/021518.html
<snip>
I just updated to 7.2 from 7.1. I did lsb_release -a and it says 7.2.1511. I haven’t rebooted yet, which items would run with new binaries, anything that isn’t running yet? Ssay I had apache running, it wouldn’t pick up new apache until a reboot, right?
I have no idea, but there are security kernel updates:
https://lists.centos.org/pipermail/centos-cr-announce/2015-Novemb er/002347.html https://lists.centos.org/pipermail/centos-cr-announce/2015-Novem ber/002347.html
https://lists.centos.org/pipermail/centos-cr-announce/2015-Decemb er/002732.html https://lists.centos.org/pipermail/centos-cr-announce/2015-Decem ber/002732.html
And those will not be active without a reboot.
Thanks to you and John R Pierce for your replies.
-wes
You can always use the "needs-restarting" script to see what you need to restart.
[Someone suggested "lsof | grep DEL | grep /usr" as an alternative. I haven't used that approach or compared it to "needs-restarting" so don't know exactly which is a better approach.]
With an update from one point release to another I would think that you'd have a rather unstable system until you do a reboot.
On 12/15/2015 04:52 AM, Richard wrote:
Date: Monday, December 14, 2015 20:38:23 -0700 From: Wes James comptekki@me.com
On Dec 14, 2015, at 4:57 PM, Johnny Hughes johnny@centos.org wrote:
On 12/14/2015 05:46 PM, Wes James wrote:
On Dec 14, 2015, at 9:37 AM, Johnny Hughes johnny@centos.org wrote:
See this announce mail here:
https://lists.centos.org/pipermail/centos-announce/2015-Decembe r/021518.html
<snip>
I just updated to 7.2 from 7.1. I did lsb_release -a and it says 7.2.1511. I haven’t rebooted yet, which items would run with new binaries, anything that isn’t running yet? Ssay I had apache running, it wouldn’t pick up new apache until a reboot, right?
I have no idea, but there are security kernel updates:
https://lists.centos.org/pipermail/centos-cr-announce/2015-Novemb er/002347.html https://lists.centos.org/pipermail/centos-cr-announce/2015-Novem ber/002347.html
https://lists.centos.org/pipermail/centos-cr-announce/2015-Decemb er/002732.html https://lists.centos.org/pipermail/centos-cr-announce/2015-Decem ber/002732.html
And those will not be active without a reboot.
Thanks to you and John R Pierce for your replies.
-wes
You can always use the "needs-restarting" script to see what you need to restart.
[Someone suggested "lsof | grep DEL | grep /usr" as an alternative. I haven't used that approach or compared it to "needs-restarting" so don't know exactly which is a better approach.]
With an update from one point release to another I would think that you'd have a rather unstable system until you do a reboot.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Hi,
the recommended way is to install yum-plugin-ps and use the 'yum ps' command...
//Zdenek
On 15 December 2015 at 12:15, Zdenek Sedlak dev@apgrco.com wrote:
On 12/15/2015 04:52 AM, Richard wrote:
Date: Monday, December 14, 2015 20:38:23 -0700 From: Wes James comptekki@me.com
On Dec 14, 2015, at 4:57 PM, Johnny Hughes johnny@centos.org wrote:
On 12/14/2015 05:46 PM, Wes James wrote:
On Dec 14, 2015, at 9:37 AM, Johnny Hughes johnny@centos.org wrote:
See this announce mail here:
https://lists.centos.org/pipermail/centos-announce/2015-Decembe r/021518.html
<snip>
I just updated to 7.2 from 7.1. I did lsb_release -a and it says 7.2.1511. I haven’t rebooted yet, which items would run with new binaries, anything that isn’t running yet? Ssay I had apache running, it wouldn’t pick up new apache until a reboot, right?
I have no idea, but there are security kernel updates:
https://lists.centos.org/pipermail/centos-cr-announce/2015-Novemb er/002347.html https://lists.centos.org/pipermail/centos-cr-announce/2015-Novem ber/002347.html
https://lists.centos.org/pipermail/centos-cr-announce/2015-Decemb er/002732.html https://lists.centos.org/pipermail/centos-cr-announce/2015-Decem ber/002732.html
And those will not be active without a reboot.
Thanks to you and John R Pierce for your replies.
-wes
You can always use the "needs-restarting" script to see what you need to restart.
[Someone suggested "lsof | grep DEL | grep /usr" as an alternative. I haven't used that approach or compared it to "needs-restarting" so don't know exactly which is a better approach.]
With an update from one point release to another I would think that you'd have a rather unstable system until you do a reboot.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Hi,
the recommended way is to install yum-plugin-ps and use the 'yum ps' command...
Well the point seems rather moot for the present update as there is no way you should not reboot after the milestone of a point release ...
On 12/15/2015 02:17 PM, James Hogarth wrote:
On 15 December 2015 at 12:15, Zdenek Sedlak dev@apgrco.com wrote:
On 12/15/2015 04:52 AM, Richard wrote:
Date: Monday, December 14, 2015 20:38:23 -0700 From: Wes James comptekki@me.com
On Dec 14, 2015, at 4:57 PM, Johnny Hughes johnny@centos.org wrote:
On 12/14/2015 05:46 PM, Wes James wrote:
> On Dec 14, 2015, at 9:37 AM, Johnny Hughes johnny@centos.org > wrote: > > See this announce mail here: > > https://lists.centos.org/pipermail/centos-announce/2015-Decembe > r/021518.html
<snip>
I just updated to 7.2 from 7.1. I did lsb_release -a and it says 7.2.1511. I haven’t rebooted yet, which items would run with new binaries, anything that isn’t running yet? Ssay I had apache running, it wouldn’t pick up new apache until a reboot, right?
I have no idea, but there are security kernel updates:
https://lists.centos.org/pipermail/centos-cr-announce/2015-Novemb er/002347.html https://lists.centos.org/pipermail/centos-cr-announce/2015-Novem ber/002347.html
https://lists.centos.org/pipermail/centos-cr-announce/2015-Decemb er/002732.html https://lists.centos.org/pipermail/centos-cr-announce/2015-Decem ber/002732.html
And those will not be active without a reboot.
Thanks to you and John R Pierce for your replies.
-wes
You can always use the "needs-restarting" script to see what you need to restart.
[Someone suggested "lsof | grep DEL | grep /usr" as an alternative. I haven't used that approach or compared it to "needs-restarting" so don't know exactly which is a better approach.]
With an update from one point release to another I would think that you'd have a rather unstable system until you do a reboot.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Hi,
the recommended way is to install yum-plugin-ps and use the 'yum ps' command...
Well the point seems rather moot for the present update as there is no way you should not reboot after the milestone of a point release ... _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
No discrepancy here ;-)
I just wanted to share this because some of the plug-ins didn't exist before and therefore not everyone is aware of them...
//Zdenek
On 12/14/2015 3:46 PM, Wes James wrote:
I just updated to 7.2 from 7.1. I did lsb_release -a and it says 7.2.1511. I haven’t rebooted yet, which items would run with new binaries, anything that isn’t running yet? Ssay I had apache running, it wouldn’t pick up new apache until a reboot, right?
most service updates will restart the service
On 15.12.2015 03:22, John R Pierce wrote:
On 12/14/2015 3:46 PM, Wes James wrote:
I just updated to 7.2 from 7.1. I did lsb_release -a and it says 7.2.1511. I haven’t rebooted yet, which items would run with new binaries, anything that isn’t running yet? Ssay I had apache running, it wouldn’t pick up new apache until a reboot, right?
most service updates will restart the service
Will they? That sound like a pretty terrible idea.
Regards, Dennis
On 12/15/2015 02:23 PM, Dennis Jacobfeuerborn wrote:
On 15.12.2015 03:22, John R Pierce wrote:
On 12/14/2015 3:46 PM, Wes James wrote:
I just updated to 7.2 from 7.1. I did lsb_release -a and it says 7.2.1511. I haven’t rebooted yet, which items would run with new binaries, anything that isn’t running yet? Ssay I had apache running, it wouldn’t pick up new apache until a reboot, right?
most service updates will restart the service
Will they? That sound like a pretty terrible idea.
Regards, Dennis
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
No they don't (opposite to e.g. Debian).
//Zdenek
Am 15.12.2015 um 14:31 schrieb Zdenek Sedlak dev@apgrco.com:
On 12/15/2015 02:23 PM, Dennis Jacobfeuerborn wrote:
On 15.12.2015 03:22, John R Pierce wrote:
On 12/14/2015 3:46 PM, Wes James wrote:
most service updates will restart the service
Will they? That sound like a pretty terrible idea.
Regards, Dennis
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
No they don't (opposite to e.g. Debian).
If updated via rpm/yum, they do a "condrestart", but OPs context is an 7.1503 to 7.1511 "upgrade". Thus, the execution environment changes significantly (glibc, kernel etc.) and this should be addressed with a reboot. If in the future only a "service" (e.g. httpd) gets an update, then rpm handles the restarting process of the running service.
-- LF
On 12/15/2015 03:51 PM, Leon Fauster wrote:
Am 15.12.2015 um 14:31 schrieb Zdenek Sedlak dev@apgrco.com:
On 12/15/2015 02:23 PM, Dennis Jacobfeuerborn wrote:
On 15.12.2015 03:22, John R Pierce wrote:
On 12/14/2015 3:46 PM, Wes James wrote:
most service updates will restart the service
Will they? That sound like a pretty terrible idea.
Regards, Dennis
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
No they don't (opposite to e.g. Debian).
If updated via rpm/yum, they do a "condrestart", but OPs context is an 7.1503 to 7.1511 "upgrade". Thus, the execution environment changes significantly (glibc, kernel etc.) and this should be addressed with a reboot. If in the future only a "service" (e.g. httpd) gets an update, then rpm handles the restarting process of the running service.
-- LF
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Thank for the explanation. When did this change? I always believed the running daemon is not touched by rpm/yum...
IMHO this is a dangerous behaviour because of possible configuration changes which need to be merged first...
//Zdenek
On Tue, Dec 15, 2015 at 04:29:12PM +0100, Zdenek Sedlak wrote:
Thank for the explanation. When did this change? I always believed the running daemon is not touched by rpm/yum...
IMHO this is a dangerous behaviour because of possible configuration changes which need to be merged first...
The change was made years ago. From the lack of screaming, you can tell that rpm is being reasonably clever about it.
Apache, for example, checks its config syntax before restarting: man apachectl, see 'graceful' and 'restart'.
-- greg
On 12/15/2015 08:51 AM, Greg Lindahl wrote:
The change was made years ago. From the lack of screaming, you can tell that rpm is being reasonably clever about it.
I can find no evidence that rpm does anything of the sort. httpd restarts on upgrade because its maintainers included a command to do so in the %posttrans scriptlet.
Apache, for example, checks its config syntax before restarting: man apachectl, see 'graceful' and 'restart'.
httpd checks its configuration syntax before *reloading* which is not what happens during an rpm upgrade. An upgrade will run "systemctl try-restart", which stops and starts the service if it is running.
On Tue, Dec 15, 2015 at 10:04:50AM -0800, Gordon Messmer wrote:
httpd checks its configuration syntax before *reloading* which is not what happens during an rpm upgrade. An upgrade will run "systemctl try-restart", which stops and starts the service if it is running.
I can think of another example of a package restarting a service:
The glibc and glibc-common packages run a command called /usr/sbin/glibc_post_upgrade.x86_64 or /usr/sbin/glibc_post_upgrade.i686 (depending on whether its an x86_64 or i686 package) in their RPM postinstall scriptlet.
It runs service sshd condrestart if it detects that /etc/rc.d/init.d/sshd exists (so, nothing on systemd-based systems). It also runs 'telinit u' too.
-
Dennis Jacobfeuerborn -
Gordon Messmer -
Greg Lindahl -
James Hogarth -
John R Pierce -
Johnny Hughes -
Jonathan Billings -
Leon Fauster -
Richard -
Wes James -
Zdenek Sedlak