[opensuse-factory] [Leap 42.1] rpmconfigcheck is not enabled by install :-?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eleanor-421:~ # systemctl status rpmconfigcheck rpmconfigcheck.service - LSB: rpm config file scan Loaded: loaded (/etc/init.d/rpmconfigcheck) Active: inactive (dead) Eleanor-421:~ # - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYOpb4ACgkQtTMYHG2NR9WkRwCdEFLutF4oIcSJ87ZNGnMw3WuS XyMAnj+27M+BLmv9YTTf7XTuGJs7iSAl =3ePP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2015-10-02 at 17:41 +0200, Carlos E. R. wrote:
Eleanor-421:~ # systemctl status rpmconfigcheck rpmconfigcheck.service - LSB: rpm config file scan Loaded: loaded (/etc/init.d/rpmconfigcheck) Active: inactive (dead)
The default for openSUSE is to install the services disabled - installing the package should not enable the service unconditionally. There are of course obvious exceptions, like with every good rule (the ones listed in systemd-presets-branding-openSUSE, see the installed file /usr/lib/systemd/system-preset/90-default-openSUSE.preset See also https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines# Enabling_service Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-10-02 17:50, Dominique Leuenberger / DimStar wrote:
On Fri, 2015-10-02 at 17:41 +0200, Carlos E. R. wrote:
Eleanor-421:~ # systemctl status rpmconfigcheck rpmconfigcheck.service - LSB: rpm config file scan Loaded: loaded (/etc/init.d/rpmconfigcheck) Active: inactive (dead)
The default for openSUSE is to install the services disabled - installing the package should not enable the service unconditionally.
Even for services that are installed by default? This particular service has been enabled by default for decades. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYOsLQACgkQtTMYHG2NR9XCJQCfe4i9cI+IN+UpWSkpADW54XJu o0UAn0TW4DYxSlBX3rady1Pm8YmdVEKK =SE6m -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Freitag, 2. Oktober 2015 schrieb Carlos E. R.:
On 2015-10-02 17:50, Dominique Leuenberger / DimStar wrote:
On Fri, 2015-10-02 at 17:41 +0200, Carlos E. R. wrote:
Eleanor-421:~ # systemctl status rpmconfigcheck rpmconfigcheck.service - LSB: rpm config file scan Loaded: loaded (/etc/init.d/rpmconfigcheck) Active: inactive (dead)
The default for openSUSE is to install the services disabled - installing the package should not enable the service unconditionally.
Even for services that are installed by default? This particular service has been enabled by default for decades.
I know, but IMHO rpmconfigcheck isn't something that should run as initscript. rpmconfigcheck searches for *.rpmnew and *.rpmorig files and then prints out the result - and with the graphical boot screen, nobody will see it. Therefore it's pointless to run it on boot. A much better option would be to run it after each zypper/libzypp operation, because that is what actually changes the rpm database and (possibly) leaves *.rpmnew and *.rpmorig files behind. Or simply run it manually from time to time whenever you have some time to cleanup the *.rpmnew and *.rpmorig files. Regards, Christian Boltz -- Die Lösung ist denkbar einfach und naheliegend: Ich bin ein Trottel. Aber das wussten wir ja schon. :-) [Ratti in suse-linux] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-10-02 23:48, Christian Boltz wrote:
I know, but IMHO rpmconfigcheck isn't something that should run as initscript.
rpmconfigcheck searches for *.rpmnew and *.rpmorig files and then prints out the result - and with the graphical boot screen, nobody will see it. Therefore it's pointless to run it on boot.
Ah. Yes. Well, in my main system I have it email me if the result is different than on the previous runs. I forgot about this.
A much better option would be to run it after each zypper/libzypp operation, because that is what actually changes the rpm database and (possibly) leaves *.rpmnew and *.rpmorig files behind.
True. But it is so slow...
Or simply run it manually from time to time whenever you have some time to cleanup the *.rpmnew and *.rpmorig files.
I believe that, if those files are not cleared, "bugs" can appear, or misbehaviours, because of the system using the wrong configuration files. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlYPA00ACgkQja8UbcUWM1xpSwD/YNEiZWU44Dxii8zC83bKBZST F9Cy7IXEFMLEaWHlfIAA/R+LrU+6FR3R8lLVusIfuDgilI4PVQ0wGdsV2+0h28/I =ej8g -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Carlos E. R. -
Carlos E. R. -
Christian Boltz -
Dominique Leuenberger / DimStar