<?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: Custom shutdown script on Redhat 7.2 in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/custom-shutdown-script-on-redhat-7-2/m-p/2790205#M2266</link>
    <description>Thanks Stefan.  You hit it on the head.  I had looked at the other set up scripts but missed the importance of those /var/lock/subsys&lt;BR /&gt; files.  Works like a charm now.</description>
    <pubDate>Wed, 21 Aug 2002 15:21:24 GMT</pubDate>
    <dc:creator>Bernie Vande Griend</dc:creator>
    <dc:date>2002-08-21T15:21:24Z</dc:date>
    <item>
      <title>Custom shutdown script on Redhat 7.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/custom-shutdown-script-on-redhat-7-2/m-p/2790202#M2263</link>
      <description>This is a strange one and seems like it shouldn't be this hard. &lt;BR /&gt;We are trying to put a script in place to shutdown Apache and Informix on reboot, powerdowns, etc.  From what I can tell all I need is a K??informix script in rc6.d, rc0.d, rc1.d linked to /etc/rc.d/init.d/informix.  We put some code in place to tell that the  script is not even being called.  The same script on start up works fine.  Is there a trick to getting a shutdown script to be initiated?</description>
      <pubDate>Tue, 20 Aug 2002 19:52:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/custom-shutdown-script-on-redhat-7-2/m-p/2790202#M2263</guid>
      <dc:creator>Bernie Vande Griend</dc:creator>
      <dc:date>2002-08-20T19:52:36Z</dc:date>
    </item>
    <item>
      <title>Re: Custom shutdown script on Redhat 7.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/custom-shutdown-script-on-redhat-7-2/m-p/2790203#M2264</link>
      <description>That should work just fine...  Can you call '/etc/init.d/informix stop' manually and have it work properly?&lt;BR /&gt;</description>
      <pubDate>Tue, 20 Aug 2002 21:02:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/custom-shutdown-script-on-redhat-7-2/m-p/2790203#M2264</guid>
      <dc:creator>Craig Kelley</dc:creator>
      <dc:date>2002-08-20T21:02:17Z</dc:date>
    </item>
    <item>
      <title>Re: Custom shutdown script on Redhat 7.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/custom-shutdown-script-on-redhat-7-2/m-p/2790204#M2265</link>
      <description>Hi :-)&lt;BR /&gt;&lt;BR /&gt;I searched for the same a few hours !&lt;BR /&gt;Linux stores whether a /etc/init.d/xxxx was already started.&lt;BR /&gt;If not the Kxxx script wouldn't never be called.&lt;BR /&gt;Have a look to the other scripts in init.d !&lt;BR /&gt;Use touch /var/lock/subsys/informix in your start part !&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 21 Aug 2002 05:04:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/custom-shutdown-script-on-redhat-7-2/m-p/2790204#M2265</guid>
      <dc:creator>Stefan Marquardt_1</dc:creator>
      <dc:date>2002-08-21T05:04:25Z</dc:date>
    </item>
    <item>
      <title>Re: Custom shutdown script on Redhat 7.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/custom-shutdown-script-on-redhat-7-2/m-p/2790205#M2266</link>
      <description>Thanks Stefan.  You hit it on the head.  I had looked at the other set up scripts but missed the importance of those /var/lock/subsys&lt;BR /&gt; files.  Works like a charm now.</description>
      <pubDate>Wed, 21 Aug 2002 15:21:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/custom-shutdown-script-on-redhat-7-2/m-p/2790205#M2266</guid>
      <dc:creator>Bernie Vande Griend</dc:creator>
      <dc:date>2002-08-21T15:21:24Z</dc:date>
    </item>
  </channel>
</rss>

