[deployment-guide/comm-rel: 123/727] Yum: +important: disabling Yum plugins; rhnplugin desc

Jaromir Hradilek jhradile at fedoraproject.org
Tue Oct 19 12:34:33 UTC 2010


commit d25cdbddeabf5bbf2dbb736a62f317bc5f9f8984
Author: Douglas Silas <dhensley at redhat.com>
Date:   Thu Jul 22 23:11:44 2010 +0200

    Yum: +important: disabling Yum plugins; rhnplugin desc

 en-US/Yum.xml |   40 +++++++++++++++++++++++++++++++++++++---
 1 files changed, 37 insertions(+), 3 deletions(-)
---
diff --git a/en-US/Yum.xml b/en-US/Yum.xml
index 1f27450..154da50 100644
--- a/en-US/Yum.xml
+++ b/en-US/Yum.xml
@@ -744,11 +744,14 @@ installonly_limit=3
           <term>installonlypkgs=<replaceable>&lt;space&gt;</replaceable>&#160;<replaceable>&lt;separated&gt;</replaceable>&#160;<replaceable>&lt;list&gt;</replaceable>&#160;<replaceable>&lt;of&gt;</replaceable>&#160;<replaceable>&lt;packages&gt;</replaceable>
           </term>
           <listitem>
-            <para>Here you can provide a space-separated list of packages which <command>yum</command> can <emphasis>install</emphasis>, but will never <emphasis>update</emphasis>. <remark>I think we should say "refer to man.conf for the list of default installonlypkgs. Also, I assume that putting this directive in /etc/yum.conf and setting it to anything—even listing nothing—overrides the default. So we should put a warning here that users should list the defaults in man yum.conf unless they are really sure they want to disable them.</remark></para>
+            <para>Here you can provide a space-separated list of packages which <command>yum</command> can <emphasis>install</emphasis>, but will never <emphasis>update</emphasis>. Refer to <command>man yum.conf</command> for the list of packages which are install-only by default. If you add the <literal>installonlypkgs</literal> directive to <filename>/etc/yum.conf</filename>, you should ensure that you list <emphasis>all</emphasis> of the packages that should be install-only, including any of those listed under the <literal>installonlypkgs</literal> section of <command>man yum.conf</command>. In particular, kernel packages should always be listed in <literal>installonlypkgs</literal> (as they are by default), and <literal>installonly_limit</literal> should always be set to a value greater than <constant>2</constant> so that a backup kernel is always available in case the default one fails to boot. Refer to <xref
+                linkend="varentry-installonly_limit_value"/> for details on the <literal>installonly_limit</literal> directive.</para>
           </listitem>
         </varlistentry>
-        <varlistentry>
-          <term>installonly_limit=<replaceable>&lt;value&gt;</replaceable></term>
+        <varlistentry
+          id="varentry-installonly_limit_value">
+          <term>installonly_limit=<replaceable>&lt;value&gt;</replaceable>
+          </term>
           <listitem>
             <para>...where <replaceable>&lt;value&gt;</replaceable> is an integer representing the maximum number of versions that can be installed simultaneously for any single package listed in the <literal>installonlypkgs</literal> directive. The defaults for the <literal>installonlypkgs</literal> directive include several different kernel packages, so be aware that changing the value of <literal>installonly_limit</literal> will also affect the maximum number of installed versions of any single kernel package. The default is therefore <literal>installonly_limit=3</literal>, and it is not recommended to decrease this value, particularly below <constant>2</constant>.</para>
           </listitem>
@@ -789,6 +792,12 @@ installonly_limit=3
             <para>...where <replaceable>&lt;value&gt;</replaceable> is one of:</para>
             <para>
               <constant>0</constant> — Disable all <application>Yum</application> plugins globally.</para>
+            <important
+              id="important-Disabling_plugins_is_not_advised-main_options">
+              <title>Disabling plugins is not advised</title>
+              <para>Disabling all plugins is not advised because certain plugins provide important <command>Yum</command> services. In particular, <application>rhnplugin</application> enables connecting to <systemitem
+                  class="systemname">Red Hat Network</systemitem>, and the security plugin allows system administrators to easily update the system with (sometimes critical) security updates. Disabling plugins globally is provided as a convenience option, and is generally only recommended when diagnosing a potential problem with <command>Yum</command>.</para>
+            </important>
             <para>
               <constant>1</constant> — Enable all <application>Yum</application> plugins globally. With <literal>plugins=1</literal>, you can still disable a specific <application>Yum</application> plugin by setting <literal>enabled=0</literal> in that plugin's configuration file. Refer to <xref
                 linkend="sec-Yum_Plugins"/> for more information about various <application>Yum</application> plugins, or to <xref
@@ -994,6 +1003,12 @@ Loaded plugins: presto, refresh-packagekit, security
 plugins=1
 </screen>
       <para>You can disable all plugins by changing this line to <command>plugins=0</command>.</para>
+      <important
+        id="important-Disabling_plugins_is_not_advised-plugins">
+        <title>Disabling plugins is not advised</title>
+        <para>Disabling all plugins is not advised because certain plugins provide important <command>Yum</command> services. In particular, <application>rhnplugin</application> enables connecting to <systemitem
+            class="systemname">Red Hat Network</systemitem>, and the security plugin allows system administrators to easily update the system with (sometimes critical) security updates. Disabling plugins globally is provided as a convenience option, and is generally only recommended when diagnosing a potential problem with <command>Yum</command>.</para>
+      </important>
       <para>Every installed plugin has its own configuration file in the <filename>/etc/yum/pluginconf.d/</filename> directory. You can set plugin-specific options in these files. For example, here is the <application>security</application> plugin's <filename>security.conf</filename> configuration file:</para>
       <example
         id="ex-A_minimal_Yum_plugin_configuration_file">
@@ -1049,6 +1064,25 @@ enabled=1
         </footnote>
  (which you should create if it does not exist), and <application>protect-packages</application> will extend protection-from-removal to those packages as well. To temporarily override package protection, use the <option>--override-protection</option> option with an applicable <command>yum</command> command.</para>
       <bridgehead
+        id="bh-rhnplugin_yum-rhn-plugin">rhnplugin (yum-rhn-plugin)</bridgehead>
+      <indexterm>
+        <primary>Yum</primary>
+        <secondary>plugins</secondary>
+        <tertiary>yum-rhn-plugin</tertiary>
+      </indexterm>
+      <indexterm>
+        <primary>Yum</primary>
+        <secondary>plugins</secondary>
+        <tertiary>rhnplugin</tertiary>
+      </indexterm>
+      <!--rhnplugin  provides Red Hat Network support for yum(8) via its plugin architecture. A system registered with Red Hat Network will be able
+       to update and install packages from Red Hat Network.-->
+      <para>The <application>rhnplugin</application> for <application>Yum</application> provides support for connecting to <systemitem
+          class="systemname">Red Hat Network</systemitem> (RHN). Systems registered with <systemitem
+          class="systemname">RHN</systemitem> are able to update and install packages from <systemitem
+          class="systemname">Red Hat Network</systemitem>.</para>
+      <para>Refer to <command>man rhnplugin</command> for more information.</para>
+      <bridgehead
         id="bh-refresh-packagekit_PackageKit-yum-plugin">refresh-packagekit (PackageKit-yum-plugin)</bridgehead>
       <indexterm>
         <primary>Yum</primary>


More information about the docs-commits mailing list