<?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: &amp;quot;system&amp;quot; call in multithreading env in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614137#M676001</link>
    <description>&amp;gt;Can I use fork/execl instead of "system"?&lt;BR /&gt;&lt;BR /&gt;Sure.  Provided you know how to implement what you are passing to system(3).</description>
    <pubDate>Wed, 28 Apr 2010 06:31:03 GMT</pubDate>
    <dc:creator>Dennis Handly</dc:creator>
    <dc:date>2010-04-28T06:31:03Z</dc:date>
    <item>
      <title>"system" call in multithreading env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614132#M675993</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I have a program in C code in which I would introduce the thread mechanisms.&lt;BR /&gt;&lt;BR /&gt;The program uses "system" call and I know that it is not thread-safe.&lt;BR /&gt;&lt;BR /&gt;My question is: can I use "system" in main-thread only? Or is it forbidden also here?&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards&lt;BR /&gt;&lt;BR /&gt;Giuseppe&lt;BR /&gt;</description>
      <pubDate>Thu, 08 Apr 2010 09:22:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614132#M675993</guid>
      <dc:creator>Fedele Giuseppe</dc:creator>
      <dc:date>2010-04-08T09:22:44Z</dc:date>
    </item>
    <item>
      <title>Re: "system" call in multithreading env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614133#M675995</link>
      <description>The problem with system(3) is that is calls fork/exec.  This means the atfork handlers have to fire off and any signal handling required to wait for the child has to be done.&lt;BR /&gt;&lt;BR /&gt;That said, I don't know if limiting it to the main thread will be good enough.</description>
      <pubDate>Thu, 08 Apr 2010 17:00:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614133#M675995</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2010-04-08T17:00:23Z</dc:date>
    </item>
    <item>
      <title>Re: "system" call in multithreading env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614134#M675996</link>
      <description>Hi,&lt;BR /&gt;could you better explain how to manage signals in such a context?&lt;BR /&gt;&lt;BR /&gt;The standard signal handling must be modified?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Giuseppe&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Apr 2010 08:29:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614134#M675996</guid>
      <dc:creator>Fedele Giuseppe</dc:creator>
      <dc:date>2010-04-27T08:29:55Z</dc:date>
    </item>
    <item>
      <title>Re: "system" call in multithreading env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614135#M675998</link>
      <description>&amp;gt;could you better explain how to manage signals in such a context?&lt;BR /&gt;&lt;BR /&gt;You may not able to do that because system(3) has to handle SIGCHLD and may mess up your handler.</description>
      <pubDate>Tue, 27 Apr 2010 08:42:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614135#M675998</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2010-04-27T08:42:58Z</dc:date>
    </item>
    <item>
      <title>Re: "system" call in multithreading env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614136#M675999</link>
      <description>Can I use fork/execl instead of "system" ?&lt;BR /&gt;&lt;BR /&gt;I know these two calls are thread safe ...&lt;BR /&gt;&lt;BR /&gt;Giuseppe</description>
      <pubDate>Tue, 27 Apr 2010 09:05:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614136#M675999</guid>
      <dc:creator>Fedele Giuseppe</dc:creator>
      <dc:date>2010-04-27T09:05:18Z</dc:date>
    </item>
    <item>
      <title>Re: "system" call in multithreading env</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614137#M676001</link>
      <description>&amp;gt;Can I use fork/execl instead of "system"?&lt;BR /&gt;&lt;BR /&gt;Sure.  Provided you know how to implement what you are passing to system(3).</description>
      <pubDate>Wed, 28 Apr 2010 06:31:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/quot-system-quot-call-in-multithreading-env/m-p/4614137#M676001</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2010-04-28T06:31:03Z</dc:date>
    </item>
  </channel>
</rss>

