Re: [opensuse] purging old kernels
On 2013-06-11 13:57:54 +0200, Marcus Meissner wrote:
There is a service called "purge-kernels" which runs on boot by default which cleans up the multiple installed kernels.
Check with "systemctl status purge-kernels".
I get the following output: purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service So something is not enabled that should be. The empty file /boot/do_purge_kernels already exists. The file /usr/lib/systemd/system/purge-kernels.service references /sbin/purge-kernels, so I simply ran this and it successfully removed the oldest of the three kernels I have installed, freeing up some space in /boot. The question then is should that service be enabled by default and why wasn't it? Running systemctl status purge-kernels again now, it is still disabled. How do I set it to enabled? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Jun 11, 2013 at 02:50:21PM +0200, Peter wrote:
On 2013-06-11 13:57:54 +0200, Marcus Meissner wrote:
There is a service called "purge-kernels" which runs on boot by default which cleans up the multiple installed kernels.
Check with "systemctl status purge-kernels".
I get the following output: purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service
So something is not enabled that should be. The empty file /boot/do_purge_kernels already exists. The file /usr/lib/systemd/system/purge-kernels.service references /sbin/purge-kernels, so I simply ran this and it successfully removed the oldest of the three kernels I have installed, freeing up some space in /boot.
The question then is should that service be enabled by default and why wasn't it? Running systemctl status purge-kernels again now, it is still disabled. How do I set it to enabled?
I released a systemd-branding-openSUSE update actually that should have enabled it. Locally you can run: systemctl enable purge-kernels to enable it. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 6/11/2013 5:52 AM, Marcus Meissner wrote:
I released a systemd-branding-openSUSE update actually that should have enabled it.
What version does that appear in? (also which repository)? -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Jun 11, 2013 at 10:50:19AM -0700, John Andersen wrote:
On 6/11/2013 5:52 AM, Marcus Meissner wrote:
I released a systemd-branding-openSUSE update actually that should have enabled it.
What version does that appear in? (also which repository)?
As people say it doesnt work ... well. The update repo. http://download.opensuse.org/update/12.3/ Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Peter wrote:
I get the following output: purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service
I get the same. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 15:51, James Knott wrote:
Peter wrote:
I get the following output: purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service
I get the same.
Me too. Telcontar:~ # systemctl status purge-kernels.service purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service Telcontar:~ # systemctl enable purge-kernels.service ln -s '/usr/lib/systemd/system/purge-kernels.service' '/etc/systemd/system/multi-user.target.wants/purge-kernels.service' Telcontar:~ # I upgraded to 12.3 last Saturday... - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3MIoACgkQIvFNjefEBxplZwCeIL31prtIL77qZvUcODBnA0QU TiUAnilCrG9DTtpoC0SwvyvUql2tM17i =HK2B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Jun 11, 2013 at 04:13:30PM +0200, Carlos E. R. wrote:
On 2013-06-11 15:51, James Knott wrote:
Peter wrote:
I get the following output: purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service
I get the same.
Me too.
Telcontar:~ # systemctl status purge-kernels.service purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service
Telcontar:~ # systemctl enable purge-kernels.service ln -s '/usr/lib/systemd/system/purge-kernels.service' '/etc/systemd/system/multi-user.target.wants/purge-kernels.service' Telcontar:~ #
I upgraded to 12.3 last Saturday...
Did you install the online updates? Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 16:17, Marcus Meissner wrote:
I upgraded to 12.3 last Saturday...
Did you install the online updates?
All of them. System is fully patched and updated... I wrote the documentation on off-line upgrades... I should know how to do it ;-) <http://en.opensuse.org/SDB:Offline_upgrade> - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3Mr0ACgkQIvFNjefEBxofcwCg2DDcHBdcfjmiD+Xj14/4T3JY z1gAn36bAXC11QS8bfdLOwb2hu20ME5k =XCNJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Tue, 11 Jun 2013 16:17:52 +0200 Marcus Meissner <meissner@suse.de> пишет:
On Tue, Jun 11, 2013 at 04:13:30PM +0200, Carlos E. R. wrote:
On 2013-06-11 15:51, James Knott wrote:
Peter wrote:
I get the following output: purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service
I get the same.
Me too.
Telcontar:~ # systemctl status purge-kernels.service purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service
Telcontar:~ # systemctl enable purge-kernels.service ln -s '/usr/lib/systemd/system/purge-kernels.service' '/etc/systemd/system/multi-user.target.wants/purge-kernels.service' Telcontar:~ #
I upgraded to 12.3 last Saturday...
Did you install the online updates?
systemd-presets-branding-openSUSE-0.2.0-2.5.1.noarch post script does not reapply systemd presets, so updates won't really help here unless it is done somewhere else. Unfortunately this is one of those cases that can really be fixed only during installation.
Ciao, Marcus
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 17:28, Andrey Borzenkov wrote:
systemd-presets-branding-openSUSE-0.2.0-2.5.1.noarch post script does not reapply systemd presets, so updates won't really help here unless it is done somewhere else. Unfortunately this is one of those cases that can really be fixed only during installation.
Don't rpms trigger running scripts? - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3R7QACgkQIvFNjefEBxpTYQCgvWtKbKWiD8fEgmsZVTEaprTN +8wAnjtw54IYvVwXyV50VdlHUWLRHybM =jqga -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 17:52, Carlos E. R. wrote:
On 2013-06-11 17:28, Andrey Borzenkov wrote:
systemd-presets-branding-openSUSE-0.2.0-2.5.1.noarch post script does not reapply systemd presets, so updates won't really help here unless it is done somewhere else. Unfortunately this is one of those cases that can really be fixed only during installation.
Don't rpms trigger running scripts?
Opps, "doesn't". - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3SBAACgkQIvFNjefEBxrOLwCgnDrdOzm4UH2NLrT54PctbacX bMMAnj9cX/bf9+aCJTZILyazrC34O8BS =OnHG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Tue, 11 Jun 2013 17:53:52 +0200 "Carlos E. R." <robin.listas@telefonica.net> пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-06-11 17:52, Carlos E. R. wrote:
On 2013-06-11 17:28, Andrey Borzenkov wrote:
systemd-presets-branding-openSUSE-0.2.0-2.5.1.noarch post script does not reapply systemd presets, so updates won't really help here unless it is done somewhere else. Unfortunately this is one of those cases that can really be fixed only during installation.
Don't rpms trigger running scripts?
Opps, "doesn't".
Not sure I understand the question. In any case - RPM update should not change enabled/disabled status of service. Update has no way to know, whether service is disabled due to suboptimal default in the past or due to explicit user decision (unless we want to introduce third state "default"). So changing defaults will not magically fix the problem for existing installation. This is similar to networking issue which was fixed in post-GA update but it was too late, because it really had to be applied during installation. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG3TFkACgkQR6LMutpd94zHNwCfUm3yvAtgMMqBA+H8GwnhUbx7 bCMAoIzd9ouOYGuNJFwlqCdN9+RNoug6 =VAWd -----END PGP SIGNATURE----- N▀╖╡ФЛr╦⌡yИ ┼Z)z{.╠О╝·к⌡╠йБmЙ)z{.╠Й+│: ╒{Zrшaz▄'z╥╕j)h╔ИЛ╨г╬ё ч╝┼^·к╛z┼Ю
On Tue, Jun 11, 2013 at 11:52 AM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-06-11 17:28, Andrey Borzenkov wrote:
systemd-presets-branding-openSUSE-0.2.0-2.5.1.noarch post script does not reapply systemd presets, so updates won't really help here unless it is done somewhere else. Unfortunately this is one of those cases that can really be fixed only during installation.
Don't rpms trigger running scripts?
I've not been following this thread, but a RPM can optionally run a series of commands after a RPM is installed. There is a %post section of the specfile that designates what is done. Andrey is talking about that section of the specfile when he talks about the "post script". Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 18:39, Greg Freemyer wrote:
On Tue, Jun 11, 2013 at 11:52 AM, Carlos E. R. <> wrote:
Doesn't rpms trigger running scripts?
I've not been following this thread, but a RPM can optionally run a series of commands after a RPM is installed.
Yes, that is what I meant. But apparently it is not correct to do so in this case because it can change the admin decision. However, maybe it can be determined (rpm -V package) if a file has been modified locally or not. It it hasn't, then the admin is using defaults and the change could be applied by the update. Perhaps. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3ouYACgkQIvFNjefEBxop5gCeNxmhF6dPVHXuOSasUXHqnI1L MDQAnA5djj1r3Rh2GY1W6gd2BgHCDo1K =7qXG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Il 11/06/2013 09:50, Peter ha scritto:
On 2013-06-11 13:57:54 +0200, Marcus Meissner wrote:
There is a service called "purge-kernels" which runs on boot by default which cleans up the multiple installed kernels.
Check with "systemctl status purge-kernels".
I get the following output: purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service
So something is not enabled that should be. The empty file /boot/do_purge_kernels already exists. The file /usr/lib/systemd/system/purge-kernels.service references /sbin/purge-kernels, so I simply ran this and it successfully removed the oldest of the three kernels I have installed, freeing up some space in /boot.
The question then is should that service be enabled by default and why wasn't it? Running systemctl status purge-kernels again now, it is still disabled. How do I set it to enabled?
Hello, I was curious to check my setup, since also I use a separate (limited space) of /boot partition and I get this response: marco@linux-turion64:~> sudo systemctl status purge-kernels.service purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; enabled) Active: inactive (dead) start condition failed at Sat, 2013-06-15 12:43:52 BRT; 9min ago CGroup: name=systemd:/system/purge-kernels.service Why it says "start condition failed"? Cheers, -- Marco Calistri (amdturion) opensuse 12.3 (Dartmouth) 64 bit - Kernel 3.7.10-1.4-desktop Gnome 3.6.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday, June 15, 2013 01:04:05 PM Marco Calistri wrote:
Il 11/06/2013 09:50, Peter ha scritto:
On 2013-06-11 13:57:54 +0200, Marcus Meissner wrote:
There is a service called "purge-kernels" which runs on boot by default which cleans up the multiple installed kernels.
Check with "systemctl status purge-kernels".
I get the following output: purge-kernels.service - Purge old kernels
Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service;
disabled)
Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service
So something is not enabled that should be. The empty file /boot/do_purge_kernels already exists. The file /usr/lib/systemd/system/purge-kernels.service references /sbin/purge-kernels, so I simply ran this and it successfully removed the oldest of the three kernels I have installed, freeing up some space in /boot.
The question then is should that service be enabled by default and why wasn't it? Running systemctl status purge-kernels again now, it is still disabled. How do I set it to enabled?
Hello,
I was curious to check my setup, since also I use a separate (limited space) of /boot partition and I get this response:
marco@linux-turion64:~> sudo systemctl status purge-kernels.service purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; enabled) Active: inactive (dead) start condition failed at Sat, 2013-06-15 12:43:52 BRT; 9min ago
CGroup: name=systemd:/system/purge-kernels.service
Why it says "start condition failed"?
Cheers,
-- Marco Calistri (amdturion) opensuse 12.3 (Dartmouth) 64 bit - Kernel 3.7.10-1.4-desktop Gnome 3.6.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I just checked mine after reading your thread. I have the same message: [CODE] ------------ rpl7:~> systemctl status purge-kernels purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; enabled) Active: inactive (dead) start condition failed at Sat, 2013-06-15 08:38:31 PDT; 32min ago CGroup: name=systemd:/system/purge-kernels.service [/CODE] Never noticed before. Could have been an update I did yesterday. Have you reported this as a bug? Russ -- openSUSE 12.3(Linux 3.7.10-1.11-desktop x86_64)|KDE 4.10.4 "release 569"|Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS(NVIDIA-Linux-x86_64-319.17) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Il 15/06/2013 13:13, Upscope ha scritto:
On Saturday, June 15, 2013 01:04:05 PM Marco Calistri wrote:
Il 11/06/2013 09:50, Peter ha scritto:
On 2013-06-11 13:57:54 +0200, Marcus Meissner wrote:
There is a service called "purge-kernels" which runs on boot by default which cleans up the multiple installed kernels.
Check with "systemctl status purge-kernels".
I get the following output: purge-kernels.service - Purge old kernels
Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service;
disabled)
Active: inactive (dead) CGroup: name=systemd:/system/purge-kernels.service
So something is not enabled that should be. The empty file /boot/do_purge_kernels already exists. The file /usr/lib/systemd/system/purge-kernels.service references /sbin/purge-kernels, so I simply ran this and it successfully removed the oldest of the three kernels I have installed, freeing up some space in /boot.
The question then is should that service be enabled by default and why wasn't it? Running systemctl status purge-kernels again now, it is still disabled. How do I set it to enabled?
Hello,
I was curious to check my setup, since also I use a separate (limited space) of /boot partition and I get this response:
marco@linux-turion64:~> sudo systemctl status purge-kernels.service purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; enabled) Active: inactive (dead) start condition failed at Sat, 2013-06-15 12:43:52 BRT; 9min ago
CGroup: name=systemd:/system/purge-kernels.service
Why it says "start condition failed"?
Cheers,
-- Marco Calistri (amdturion) opensuse 12.3 (Dartmouth) 64 bit - Kernel 3.7.10-1.4-desktop Gnome 3.6.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I just checked mine after reading your thread. I have the same message: [CODE] ------------ rpl7:~> systemctl status purge-kernels purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; enabled) Active: inactive (dead) start condition failed at Sat, 2013-06-15 08:38:31 PDT; 32min ago CGroup: name=systemd:/system/purge-kernels.service [/CODE]
Never noticed before. Could have been an update I did yesterday.
Have you reported this as a bug?
Russ
No Russ I haven't! Cheers, -- Marco Calistri (amdturion) opensuse 12.3 (Dartmouth) 64 bit - Kernel 3.7.10-1.4-desktop Gnome 3.6.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sat, 15 Jun 2013 13:04:05 -0300 Marco Calistri <marco.calistri@yahoo.com.br> пишет:
Why it says "start condition failed"?
Because you have no kernels to purge. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Il 15/06/2013 13:36, Andrey Borzenkov ha scritto:
В Sat, 15 Jun 2013 13:04:05 -0300 Marco Calistri <marco.calistri@yahoo.com.br> пишет:
Why it says "start condition failed"?
Because you have no kernels to purge.
Obvious! Then all is right so far. Thanks Andrey! Cheers, -- Marco Calistri (amdturion) opensuse 12.3 (Dartmouth) 64 bit - Kernel 3.7.10-1.11-desktop Gnome 3.6.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Andrey Borzenkov -
Carlos E. R. -
Greg Freemyer -
James Knott -
John Andersen -
Marco Calistri -
Marcus Meissner -
Peter -
Upscope