<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why eliminate unused modules in a package? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/why-eliminate-unused-modules-in-a-package/m-p/4675979#M667064</link>
    <description>Hi Stephen&lt;BR /&gt;&lt;BR /&gt;You are correct that no function calls were removed from the control files.  The only changes made were to add a call to our script in the customer_defined_run_cmds and the customer_defined_halt_cmds functions.  No one has ever suggested making other changes to the control files other than in the parameters section.&lt;BR /&gt;&lt;BR /&gt;It sounds like there is little point in cleaning up the configuration file.&lt;BR /&gt;&lt;BR /&gt;Hi Matti&lt;BR /&gt;&lt;BR /&gt;Your point is well taken and it is probably the one reason with any basis to do the cleanup.  However, in my case there is more likelihood of causing a problem by making a mistake when doing the cleanup.&lt;BR /&gt;&lt;BR /&gt;Thank you both for your input!</description>
    <pubDate>Tue, 17 Aug 2010 19:21:37 GMT</pubDate>
    <dc:creator>Ken Englander</dc:creator>
    <dc:date>2010-08-17T19:21:37Z</dc:date>
    <item>
      <title>Why eliminate unused modules in a package?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/why-eliminate-unused-modules-in-a-package/m-p/4675976#M667061</link>
      <description>We have a LOT of clusters that will be migrating from 11.17.01 to 11.19 and to modular packages.  I "like" the idea of cleaning up the packages so they only reference modules actually being used.  However, I am wondering are there good reasons to eliminate the unused modules?  The cmmigratepkg command generates ALL the modules available so cleanup or creation from scratch is the only way to eliminate unused modules.&lt;BR /&gt;&lt;BR /&gt;I would guess that startup and shutdown of a package would be a bit quicker but other than that I am not sure what other good reasons might justify cleaning up the packages.  Also, to me it would be a best practice to eliminate the unused modules.&lt;BR /&gt;&lt;BR /&gt;Any input would be appreciated?</description>
      <pubDate>Tue, 17 Aug 2010 14:12:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/why-eliminate-unused-modules-in-a-package/m-p/4675976#M667061</guid>
      <dc:creator>Ken Englander</dc:creator>
      <dc:date>2010-08-17T14:12:09Z</dc:date>
    </item>
    <item>
      <title>Re: Why eliminate unused modules in a package?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/why-eliminate-unused-modules-in-a-package/m-p/4675977#M667062</link>
      <description>Legacy package control scripts run all script functions whether or not parameters were defined in the top part of the scripts.&lt;BR /&gt;&lt;BR /&gt;My bet is you did not delete function calls in legacy package scripts if the related parameter was not identified.&lt;BR /&gt;&lt;BR /&gt;With modular packages, module "sg/all" includes all standard modules (equivalent of a complete package control script).  So, though all standard modules may be identified, package start/stop time should be nearly equivalent to a legacy control script.&lt;BR /&gt;&lt;BR /&gt;Compare the number of modules identified in the package configuration file to those listed in /etc/cmcluster/modules/sg/all.  If there are no more, then I wouldn't burn the time cleaning out unused modules.</description>
      <pubDate>Tue, 17 Aug 2010 17:49:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/why-eliminate-unused-modules-in-a-package/m-p/4675977#M667062</guid>
      <dc:creator>Stephen Doud</dc:creator>
      <dc:date>2010-08-17T17:49:03Z</dc:date>
    </item>
    <item>
      <title>Re: Why eliminate unused modules in a package?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/why-eliminate-unused-modules-in-a-package/m-p/4675978#M667063</link>
      <description>It would also minimize the amount of code run at package startup/shutdown, which would make troubleshooting easier in case there is a problem. Less code = less places where things can go wrong.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Tue, 17 Aug 2010 18:00:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/why-eliminate-unused-modules-in-a-package/m-p/4675978#M667063</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2010-08-17T18:00:53Z</dc:date>
    </item>
    <item>
      <title>Re: Why eliminate unused modules in a package?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/why-eliminate-unused-modules-in-a-package/m-p/4675979#M667064</link>
      <description>Hi Stephen&lt;BR /&gt;&lt;BR /&gt;You are correct that no function calls were removed from the control files.  The only changes made were to add a call to our script in the customer_defined_run_cmds and the customer_defined_halt_cmds functions.  No one has ever suggested making other changes to the control files other than in the parameters section.&lt;BR /&gt;&lt;BR /&gt;It sounds like there is little point in cleaning up the configuration file.&lt;BR /&gt;&lt;BR /&gt;Hi Matti&lt;BR /&gt;&lt;BR /&gt;Your point is well taken and it is probably the one reason with any basis to do the cleanup.  However, in my case there is more likelihood of causing a problem by making a mistake when doing the cleanup.&lt;BR /&gt;&lt;BR /&gt;Thank you both for your input!</description>
      <pubDate>Tue, 17 Aug 2010 19:21:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/why-eliminate-unused-modules-in-a-package/m-p/4675979#M667064</guid>
      <dc:creator>Ken Englander</dc:creator>
      <dc:date>2010-08-17T19:21:37Z</dc:date>
    </item>
  </channel>
</rss>

