<?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: Monitoring Stdout in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-stdout/m-p/3049372#M719086</link>
    <description>does re direction to file not work when you call the scripts?</description>
    <pubDate>Thu, 14 Aug 2003 19:25:04 GMT</pubDate>
    <dc:creator>doug mielke</dc:creator>
    <dc:date>2003-08-14T19:25:04Z</dc:date>
    <item>
      <title>Monitoring Stdout</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-stdout/m-p/3049371#M719085</link>
      <description>I am trying to figure out a way to monitor stdout.   I have several C and Perl apps running together on an 11i machine and I am getting some inconsistant behavior and I suspect it may be due to stdout sharing between the 2 progs.&lt;BR /&gt;&lt;BR /&gt;Can anyone tell me how to monitor stdout?&lt;BR /&gt;&lt;BR /&gt;-Scott</description>
      <pubDate>Thu, 14 Aug 2003 19:14:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-stdout/m-p/3049371#M719085</guid>
      <dc:creator>Scott McDade</dc:creator>
      <dc:date>2003-08-14T19:14:15Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring Stdout</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-stdout/m-p/3049372#M719086</link>
      <description>does re direction to file not work when you call the scripts?</description>
      <pubDate>Thu, 14 Aug 2003 19:25:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-stdout/m-p/3049372#M719086</guid>
      <dc:creator>doug mielke</dc:creator>
      <dc:date>2003-08-14T19:25:04Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring Stdout</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-stdout/m-p/3049373#M719087</link>
      <description>How are the processes communicating with one another?&lt;BR /&gt;Is one writing to stdout what the other is reading from its stdin?&lt;BR /&gt;What do your pipes look like?&lt;BR /&gt;&lt;BR /&gt;Sometimes buffering is getting in the way and mangling the correct sequence of communication (a common issue in IPC).&lt;BR /&gt;&lt;BR /&gt;I cannot tell what to do in C.&lt;BR /&gt;I&lt;BR /&gt;n Perl it is advisable to enforce autoflushing in your Perl code by defining the special variable "$|".&lt;BR /&gt;&lt;BR /&gt;Usual Perl idioms to this end are:&lt;BR /&gt;&lt;BR /&gt;$|++;&lt;BR /&gt;# or&lt;BR /&gt;$| = 1;&lt;BR /&gt;&lt;BR /&gt;# or if you have to flush other file handles&lt;BR /&gt;select((select(HANDLE), $|++)[0]);&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If you don't mind importing some other code you could also use the IO::Handle (or IO::File, actually inheriting from IO::Handle)module that offer an autoflush method that avoids the arcane select idiom above.&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Aug 2003 05:19:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/monitoring-stdout/m-p/3049373#M719087</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2003-08-15T05:19:37Z</dc:date>
    </item>
  </channel>
</rss>

