<?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 Interrupt a system call in progress in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/interrupt-a-system-call-in-progress/m-p/3581521#M832672</link>
    <description>I am trying to lock an open file using fcntl call.&lt;BR /&gt;Assuming all the parameters to the call are valid, the only way to fail the call ( for my testing purpose) is to generate an interrupt when the call is in progress(Let me knw in case there is any other way).&lt;BR /&gt;How can we ensure an interrupt generation when fcntl call is under progress ?&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 13 Jul 2005 06:36:00 GMT</pubDate>
    <dc:creator>Pankaj Agrawal</dc:creator>
    <dc:date>2005-07-13T06:36:00Z</dc:date>
    <item>
      <title>Interrupt a system call in progress</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/interrupt-a-system-call-in-progress/m-p/3581521#M832672</link>
      <description>I am trying to lock an open file using fcntl call.&lt;BR /&gt;Assuming all the parameters to the call are valid, the only way to fail the call ( for my testing purpose) is to generate an interrupt when the call is in progress(Let me knw in case there is any other way).&lt;BR /&gt;How can we ensure an interrupt generation when fcntl call is under progress ?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 13 Jul 2005 06:36:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/interrupt-a-system-call-in-progress/m-p/3581521#M832672</guid>
      <dc:creator>Pankaj Agrawal</dc:creator>
      <dc:date>2005-07-13T06:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: Interrupt a system call in progress</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/interrupt-a-system-call-in-progress/m-p/3581522#M832673</link>
      <description>Actually, I don't think you can. If you do a man fcntl, you will find that none of the error conditions set errno = EINTR. This strongly suggests that fcntl() can't be interupted (or more properly, a signal can't be delivered to the process) because the process is then in a priority level higher than that where signals can be acted upon. This is rather common for i/o operations and is the reason that processes waiting on i/o can't be killed -- even with a kill -9. For your purposes, you would be better served to set up a situation where errno is set to EDEADLCK --- that should be a rigorous and realistic test scenario.</description>
      <pubDate>Wed, 13 Jul 2005 07:01:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/interrupt-a-system-call-in-progress/m-p/3581522#M832673</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-07-13T07:01:20Z</dc:date>
    </item>
  </channel>
</rss>

