<?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: using tee pull script output into a log in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/using-tee-pull-script-output-into-a-log/m-p/5156505#M684110</link>
    <description>Thanks Jeff.. That did it..</description>
    <pubDate>Wed, 11 Feb 2009 20:41:51 GMT</pubDate>
    <dc:creator>rmueller58</dc:creator>
    <dc:date>2009-02-11T20:41:51Z</dc:date>
    <item>
      <title>using tee pull script output into a log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-tee-pull-script-output-into-a-log/m-p/5156502#M684107</link>
      <description>I have rebuilt a major script, and would like to define some logging mechanism to watch for error conditions in the script that might occur. &lt;BR /&gt;&lt;BR /&gt;What is the process of creating a "tee" ? &lt;BR /&gt;&lt;BR /&gt;Say for example in this code section: &lt;BR /&gt;I want to log files being processed by this script. The 1st section looks at file contained in a directory. &lt;BR /&gt;##### LOCAL FILE NAME EXTRACT #####&lt;BR /&gt;for fn1 in `find -type f -mmin -60 -print` |tee echo $fn1 &amp;gt;&amp;gt; ${LOG_FIL} &lt;BR /&gt;&lt;BR /&gt;I am curious if the "redirection" in my find command would work? &lt;BR /&gt;I have several places within the code I would like to append to a daily log &lt;BR /&gt;&lt;BR /&gt;I appreciate the info.. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Feb 2009 19:49:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-tee-pull-script-output-into-a-log/m-p/5156502#M684107</guid>
      <dc:creator>rmueller58</dc:creator>
      <dc:date>2009-02-11T19:49:03Z</dc:date>
    </item>
    <item>
      <title>Re: using tee pull script output into a log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-tee-pull-script-output-into-a-log/m-p/5156503#M684108</link>
      <description>or would it be: &lt;BR /&gt;or fn1 in `find -type f -mmin -60 -print` |\tee echo $fn1 &amp;gt;&amp;gt; ${LOG_FIL} &lt;BR /&gt;&lt;BR /&gt;so as to force a carriage return? &lt;BR /&gt;</description>
      <pubDate>Wed, 11 Feb 2009 19:51:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-tee-pull-script-output-into-a-log/m-p/5156503#M684108</guid>
      <dc:creator>rmueller58</dc:creator>
      <dc:date>2009-02-11T19:51:03Z</dc:date>
    </item>
    <item>
      <title>Re: using tee pull script output into a log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-tee-pull-script-output-into-a-log/m-p/5156504#M684109</link>
      <description>&lt;!--!*#--&gt;tee is used to send output to a file as well as to the stdin (typically the screen). Use in your context would be:&lt;BR /&gt;&lt;BR /&gt;for fn1 in `find -type f -mmin -60 -print`&lt;BR /&gt;do&lt;BR /&gt;  echo $fn1 | tee -a ${LOG_FIL}&lt;BR /&gt;done</description>
      <pubDate>Wed, 11 Feb 2009 20:40:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-tee-pull-script-output-into-a-log/m-p/5156504#M684109</guid>
      <dc:creator>Jeff_Traigle</dc:creator>
      <dc:date>2009-02-11T20:40:25Z</dc:date>
    </item>
    <item>
      <title>Re: using tee pull script output into a log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-tee-pull-script-output-into-a-log/m-p/5156505#M684110</link>
      <description>Thanks Jeff.. That did it..</description>
      <pubDate>Wed, 11 Feb 2009 20:41:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-tee-pull-script-output-into-a-log/m-p/5156505#M684110</guid>
      <dc:creator>rmueller58</dc:creator>
      <dc:date>2009-02-11T20:41:51Z</dc:date>
    </item>
  </channel>
</rss>

