<?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 core file in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623993#M39299</link>
    <description>Is it possible to change the location for when a core file is generated, it is usally in / but this directory is not large enough to cope with it. If a hard link from a created file called core in / was used would this work or does the system just generate a new core and not log to the created one.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;TIA&lt;BR /&gt;</description>
    <pubDate>Mon, 03 Dec 2001 14:58:34 GMT</pubDate>
    <dc:creator>Arthur_3</dc:creator>
    <dc:date>2001-12-03T14:58:34Z</dc:date>
    <item>
      <title>core file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623993#M39299</link>
      <description>Is it possible to change the location for when a core file is generated, it is usally in / but this directory is not large enough to cope with it. If a hard link from a created file called core in / was used would this work or does the system just generate a new core and not log to the created one.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;TIA&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Dec 2001 14:58:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623993#M39299</guid>
      <dc:creator>Arthur_3</dc:creator>
      <dc:date>2001-12-03T14:58:34Z</dc:date>
    </item>
    <item>
      <title>Re: core file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623994#M39300</link>
      <description>Hi Arthur,&lt;BR /&gt;&lt;BR /&gt;The location is dependent on the process that generates the core. So, it is not a hard and fast rule that the core is always in /. Your solutions works if you don't want any core to stay in /. &lt;BR /&gt;&lt;BR /&gt;You can do like this&lt;BR /&gt;&lt;BR /&gt;#ln -s /file_system/core /core&lt;BR /&gt;&lt;BR /&gt;-Sri&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Dec 2001 15:04:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623994#M39300</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2001-12-03T15:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: core file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623995#M39301</link>
      <description>Hi,&lt;BR /&gt;In most scripts (those you "submit" from crontab for example) you can simply do this &lt;BR /&gt;by putting an cd /to_directory_where_you_want&lt;BR /&gt;in front of the "essential" command ...&lt;BR /&gt;For example&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;cd /opt/tivoli&lt;BR /&gt;/opt/tivoli/tsm/client/ba/bin/dsmc ...&lt;BR /&gt;&lt;BR /&gt;A coredump from dsmc would then be in /opt/tivoli ...&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Tom Geudens&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Dec 2001 15:07:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623995#M39301</guid>
      <dc:creator>Tom Geudens</dc:creator>
      <dc:date>2001-12-03T15:07:04Z</dc:date>
    </item>
    <item>
      <title>Re: core file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623996#M39302</link>
      <description>Hi ,&lt;BR /&gt;&lt;BR /&gt;Identify the directory where core file normaly genarates and then have a symbolic link to that perticular directory&lt;BR /&gt;This way no corefiles left around hogging disk space. &lt;BR /&gt;&lt;BR /&gt;eg. ln -s /coredirectory /tmp/core &lt;BR /&gt;&lt;BR /&gt;Also if you want to limit the size of the core use ulimit &lt;BR /&gt;&lt;BR /&gt;In .profile file add ulimit -c 0&lt;BR /&gt;This works for posix shell&lt;BR /&gt;&lt;BR /&gt;Goodluck,&lt;BR /&gt;-USA..</description>
      <pubDate>Mon, 03 Dec 2001 15:10:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623996#M39302</guid>
      <dc:creator>Uday_S_Ankolekar</dc:creator>
      <dc:date>2001-12-03T15:10:50Z</dc:date>
    </item>
    <item>
      <title>Re: core file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623997#M39303</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If you don't need the 'core' file, why don't you just&lt;BR /&gt;&lt;BR /&gt;ulimit -c 0&lt;BR /&gt;&lt;BR /&gt;which will set the limit size of the core file to 0 -&amp;gt; it won't take any disk space ;)&lt;BR /&gt;&lt;BR /&gt;ulimit -a&lt;BR /&gt;&lt;BR /&gt;will show you the current settings.&lt;BR /&gt;&lt;BR /&gt;E.</description>
      <pubDate>Mon, 03 Dec 2001 15:13:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623997#M39303</guid>
      <dc:creator>Eugen Cocalea</dc:creator>
      <dc:date>2001-12-03T15:13:43Z</dc:date>
    </item>
    <item>
      <title>Re: core file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623998#M39304</link>
      <description>Hello, &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks for the info to all...&lt;BR /&gt;&lt;BR /&gt;Uday, if th core file is generated in / surelly I cant just to a link from /?? Sorry, my HP-UX knowledge is very limited:-)&lt;BR /&gt;&lt;BR /&gt;TIA</description>
      <pubDate>Mon, 03 Dec 2001 15:36:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623998#M39304</guid>
      <dc:creator>Arthur_3</dc:creator>
      <dc:date>2001-12-03T15:36:52Z</dc:date>
    </item>
    <item>
      <title>Re: core file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623999#M39305</link>
      <description>Hi Arthur,&lt;BR /&gt;&lt;BR /&gt;As others have indicated, you are nearly right concerning the link.  A hard link won't work because it must be in the same filesystem.  Use a symbolic (soft) link to get around that.&lt;BR /&gt;&lt;BR /&gt;As info, core files are re-used.  That is to say, the inode number is not changed when a process overwrites a core file.  That is true of the regular file "core" whether it is referenced by a symlink or not.&lt;BR /&gt;&lt;BR /&gt;You are also correct that you can't have / as a symlink.  However, you can have /core as a symlink.&lt;BR /&gt;&lt;BR /&gt;If uncertain what process is creating the core file, do what core.&lt;BR /&gt;&lt;BR /&gt;Darrell</description>
      <pubDate>Mon, 03 Dec 2001 16:15:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/core-file/m-p/2623999#M39305</guid>
      <dc:creator>Darrell Allen</dc:creator>
      <dc:date>2001-12-03T16:15:55Z</dc:date>
    </item>
  </channel>
</rss>

