<?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: Stopping core dump in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/stopping-core-dump/m-p/4120181#M314684</link>
    <description>AS Dennis indicates, the standard POSIX shell (not Bourne) has ulimit -c. The problem with mkdir is that you have to do this in every possible directory that a core might occur -- kind of hard to predict. ulimit sets the environment and if you are using ksh, there are many ulimit values you cannot set in ksh. However, you can change your shell to /usr/bin/sh with the chsh command, then add the ulimit line in your .profile and at the end of .profile, run ksh. (you will find the POSIX shell is almost identical to ksh so the last step may not be necessary)</description>
    <pubDate>Sat, 22 Dec 2007 03:49:28 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2007-12-22T03:49:28Z</dc:date>
    <item>
      <title>Stopping core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/stopping-core-dump/m-p/4120177#M314680</link>
      <description>I have this 11.0 box that keeps dumping core, apparently due to SSH (as file core reveals) &lt;BR /&gt;&lt;BR /&gt;I would like to set core size to 0, so it doesn't dump core anymore, how do I do that?&lt;BR /&gt;</description>
      <pubDate>Fri, 21 Dec 2007 19:36:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/stopping-core-dump/m-p/4120177#M314680</guid>
      <dc:creator>dictum9</dc:creator>
      <dc:date>2007-12-21T19:36:46Z</dc:date>
    </item>
    <item>
      <title>Re: Stopping core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/stopping-core-dump/m-p/4120178#M314681</link>
      <description>hi;&lt;BR /&gt;&lt;BR /&gt;please read thread &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do;HP-FORUMS-S-WPA-IDX=HqmZQtlLfpLynKym6JvpJv6y1LC1BvWy8hmG8hSNMRWzGfpMfBpl!-2116547071!-2079080828?threadId=1090127" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do;HP-FORUMS-S-WPA-IDX=HqmZQtlLfpLynKym6JvpJv6y1LC1BvWy8hmG8hSNMRWzGfpMfBpl!-2116547071!-2079080828?threadId=1090127&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Hasan..</description>
      <pubDate>Fri, 21 Dec 2007 20:21:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/stopping-core-dump/m-p/4120178#M314681</guid>
      <dc:creator>Hasan  Atasoy</dc:creator>
      <dc:date>2007-12-21T20:21:08Z</dc:date>
    </item>
    <item>
      <title>Re: Stopping core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/stopping-core-dump/m-p/4120179#M314682</link>
      <description>so, ulimit does not exist in 11.0&lt;BR /&gt;&lt;BR /&gt;Per advice, I did:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;touch /core&lt;BR /&gt;chmod 444 /core&lt;BR /&gt;&lt;BR /&gt;This means a new core dump should not be able to write to this one.</description>
      <pubDate>Fri, 21 Dec 2007 21:36:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/stopping-core-dump/m-p/4120179#M314682</guid>
      <dc:creator>dictum9</dc:creator>
      <dc:date>2007-12-21T21:36:49Z</dc:date>
    </item>
    <item>
      <title>Re: Stopping core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/stopping-core-dump/m-p/4120180#M314683</link>
      <description>&amp;gt;so, ulimit does not exist in 11.0&lt;BR /&gt;&lt;BR /&gt;This is incorrect.  It exists in sh but not in ksh.  Both are real shells.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Per advice, I did: touch /core&lt;BR /&gt;&lt;BR /&gt;I would suggest you use "mkdir core" instead.  It is more obvious.</description>
      <pubDate>Fri, 21 Dec 2007 21:58:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/stopping-core-dump/m-p/4120180#M314683</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2007-12-21T21:58:03Z</dc:date>
    </item>
    <item>
      <title>Re: Stopping core dump</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/stopping-core-dump/m-p/4120181#M314684</link>
      <description>AS Dennis indicates, the standard POSIX shell (not Bourne) has ulimit -c. The problem with mkdir is that you have to do this in every possible directory that a core might occur -- kind of hard to predict. ulimit sets the environment and if you are using ksh, there are many ulimit values you cannot set in ksh. However, you can change your shell to /usr/bin/sh with the chsh command, then add the ulimit line in your .profile and at the end of .profile, run ksh. (you will find the POSIX shell is almost identical to ksh so the last step may not be necessary)</description>
      <pubDate>Sat, 22 Dec 2007 03:49:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/stopping-core-dump/m-p/4120181#M314684</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2007-12-22T03:49:28Z</dc:date>
    </item>
  </channel>
</rss>

