<?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: Script in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/script/m-p/4316514#M340127</link>
    <description>You have several options here. &lt;BR /&gt;1. Enhance your script to check dates in the syslog and only capture the most recent errors.&lt;BR /&gt;2. When the script finds errors and sends a page, have the script touch a file and use it as a flag. In the begining of the script check if the flag file exists and exit the script. You have to manually delete the flag file after you respond to the paging or have the script delete the file every few hours.&lt;BR /&gt;3. Use the "dmesg -" command to check for errors if those SCSI errors are sent to the kernel as well. The "-" option in dmesg will only show the new messages since the last time it was invoked.&lt;BR /&gt;I am sure other interesting suggestions will come up.</description>
    <pubDate>Tue, 02 Dec 2008 14:55:55 GMT</pubDate>
    <dc:creator>TTr</dc:creator>
    <dc:date>2008-12-02T14:55:55Z</dc:date>
    <item>
      <title>Script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/script/m-p/4316513#M340126</link>
      <description>I have a simple script in cron every 1/2 hour that scans syslog and looks for any scsi error. If it finds it it sends to my pager.&lt;BR /&gt;Is there a way, that when it finds an error and sends it, to stop sending the message over and over again? like a counter or something. besides, if condition is true, send message, then rename the script so cron cant find it. renaming the script is the only way I can think of ending the loop. dont have syslog-ng on this server and cant.</description>
      <pubDate>Tue, 02 Dec 2008 14:42:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/script/m-p/4316513#M340126</guid>
      <dc:creator>Nobody's Hero</dc:creator>
      <dc:date>2008-12-02T14:42:16Z</dc:date>
    </item>
    <item>
      <title>Re: Script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/script/m-p/4316514#M340127</link>
      <description>You have several options here. &lt;BR /&gt;1. Enhance your script to check dates in the syslog and only capture the most recent errors.&lt;BR /&gt;2. When the script finds errors and sends a page, have the script touch a file and use it as a flag. In the begining of the script check if the flag file exists and exit the script. You have to manually delete the flag file after you respond to the paging or have the script delete the file every few hours.&lt;BR /&gt;3. Use the "dmesg -" command to check for errors if those SCSI errors are sent to the kernel as well. The "-" option in dmesg will only show the new messages since the last time it was invoked.&lt;BR /&gt;I am sure other interesting suggestions will come up.</description>
      <pubDate>Tue, 02 Dec 2008 14:55:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/script/m-p/4316514#M340127</guid>
      <dc:creator>TTr</dc:creator>
      <dc:date>2008-12-02T14:55:55Z</dc:date>
    </item>
    <item>
      <title>Re: Script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/script/m-p/4316515#M340128</link>
      <description>You can add the condition in your script:&lt;BR /&gt;&lt;BR /&gt;if [ ! -f /etc/scsi_found ] {&lt;BR /&gt; ///check for scsi erorrs&lt;BR /&gt;  if (scsi errors found) { touch file /etc/scsi_found&lt;BR /&gt;}&lt;BR /&gt; else rm /etc/scsi_found&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;ivan&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 02 Dec 2008 14:59:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/script/m-p/4316515#M340128</guid>
      <dc:creator>Ivan Krastev</dc:creator>
      <dc:date>2008-12-02T14:59:25Z</dc:date>
    </item>
  </channel>
</rss>

