<?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: mail deadlock in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mail-deadlock/m-p/2481267#M18199</link>
    <description>My guess is that somehow there is something still open accessing this.&lt;BR /&gt;You can get lockf deadlock errors when the system is unable to give you exclusive rights to a file.  In this case your user cssdba is trying to read their mail..and for some reason the file is presently active elsewhere.&lt;BR /&gt;So you could try using the fuser command to see if you can track down what process has the file open.&lt;BR /&gt;&lt;BR /&gt;fuser -u /var/mail&lt;BR /&gt;This should give you the user and in params possibly the pid....&lt;BR /&gt;&lt;BR /&gt;Just a one thought,</description>
    <pubDate>Wed, 10 Jan 2001 16:10:11 GMT</pubDate>
    <dc:creator>Rita C Workman</dc:creator>
    <dc:date>2001-01-10T16:10:11Z</dc:date>
    <item>
      <title>mail deadlock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mail-deadlock/m-p/2481266#M18198</link>
      <description>Hello&lt;BR /&gt;&lt;BR /&gt;One of our users is receiving this message when trying to retrieve mail:&lt;BR /&gt;&lt;BR /&gt;lara:cssdba(51): mail&lt;BR /&gt;/var/mail/cssdba: Lockf deadlock detection&lt;BR /&gt;mail: can not lock on /var/mail/cssdba after 10 tries&lt;BR /&gt;&lt;BR /&gt;Can anyone suggest a solution.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 10 Jan 2001 09:40:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mail-deadlock/m-p/2481266#M18198</guid>
      <dc:creator>phil cook</dc:creator>
      <dc:date>2001-01-10T09:40:14Z</dc:date>
    </item>
    <item>
      <title>Re: mail deadlock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mail-deadlock/m-p/2481267#M18199</link>
      <description>My guess is that somehow there is something still open accessing this.&lt;BR /&gt;You can get lockf deadlock errors when the system is unable to give you exclusive rights to a file.  In this case your user cssdba is trying to read their mail..and for some reason the file is presently active elsewhere.&lt;BR /&gt;So you could try using the fuser command to see if you can track down what process has the file open.&lt;BR /&gt;&lt;BR /&gt;fuser -u /var/mail&lt;BR /&gt;This should give you the user and in params possibly the pid....&lt;BR /&gt;&lt;BR /&gt;Just a one thought,</description>
      <pubDate>Wed, 10 Jan 2001 16:10:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mail-deadlock/m-p/2481267#M18199</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2001-01-10T16:10:11Z</dc:date>
    </item>
    <item>
      <title>Re: mail deadlock</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mail-deadlock/m-p/2481268#M18200</link>
      <description>Thanks Rita&lt;BR /&gt;&lt;BR /&gt;We've had a call in at HP today &amp;amp; it would seem we need to reconfigure the nflocks kernel parameter which is a little awkward. Still looking into this but that is their opinion - I just unsure as to why this is suddenly happening on this machine - it's nice to see the whole picture i.e cause &amp;amp; effect.&lt;BR /&gt;&lt;BR /&gt;Thank you for your response anyway.&lt;BR /&gt;&lt;BR /&gt;Regards</description>
      <pubDate>Wed, 10 Jan 2001 16:50:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mail-deadlock/m-p/2481268#M18200</guid>
      <dc:creator>phil cook</dc:creator>
      <dc:date>2001-01-10T16:50:05Z</dc:date>
    </item>
  </channel>
</rss>

