<?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: syslog in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643133#M44231</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If the dump area does not have the necessary amount of space, then the&lt;BR /&gt;core dump will not contain all of information and, therefore, be less&lt;BR /&gt;useful for analyzing. If the dump device is too small, you will see a&lt;BR /&gt;message similar  on bootup&lt;BR /&gt;Your dump area should be large enough to store the entire contents of&lt;BR /&gt;RAM and the kernel.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;-USA..&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 11 Jan 2002 16:17:21 GMT</pubDate>
    <dc:creator>Uday_S_Ankolekar</dc:creator>
    <dc:date>2002-01-11T16:17:21Z</dc:date>
    <item>
      <title>syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643128#M44226</link>
      <description>I have a 10.20 HP-UX&lt;BR /&gt;When looking in /var/adm/syslog/syslog.log, the following message appears: &lt;BR /&gt;&lt;BR /&gt;Jan 11 10:44:15 sirius vmunix: WARNING: Insufficient space on dump device to save full crashdump.&lt;BR /&gt;Jan 11 10:44:15 sirius vmunix:     Only 536870912 of 536871936 bytes will be saved.&lt;BR /&gt;Jan 11 10:44:15 sirius vmunix:     Dump device table:  (start &amp;amp; size given in 1-Kbyte blocks)&lt;BR /&gt;Jan 11 10:44:15 sirius vmunix:         entry 0 - major is 31, minor is 0x18000; start = 52064, size = 524288&lt;BR /&gt;&lt;BR /&gt;What is it&lt;BR /&gt;&lt;BR /&gt;Thanks in advance, &lt;BR /&gt;frank</description>
      <pubDate>Fri, 11 Jan 2002 16:09:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643128#M44226</guid>
      <dc:creator>Francois Bariselle_3</dc:creator>
      <dc:date>2002-01-11T16:09:51Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643129#M44227</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;This will give you the explanation:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://us-support3.external.hp.com/cki/bin/doc.pl/sid=1930626f016a90f278/screen=ckiDisplayDocument?docId=200000015982397" target="_blank"&gt;http://us-support3.external.hp.com/cki/bin/doc.pl/sid=1930626f016a90f278/screen=ckiDisplayDocument?docId=200000015982397&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Shiju&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Jan 2002 16:13:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643129#M44227</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-01-11T16:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643130#M44228</link>
      <description>if you run crashconf, this will show what device a crash will dump the log to, and what is setup to be dumped.  That message is saying if you have a system crash, the space allocated will not be enough to hold the core file created.  run crashconf to see what you have setup and either add more space, or change what you will dump in case of a crash</description>
      <pubDate>Fri, 11 Jan 2002 16:14:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643130#M44228</guid>
      <dc:creator>Jeff Machols</dc:creator>
      <dc:date>2002-01-11T16:14:04Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643131#M44229</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Take a look at these threads,&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://us-support.external.hp.com/cki/bin/doc.pl/sid=1615d96002fc771b4b/screen=ckiDisplayDocument?docId=200000015982397" target="_blank"&gt;http://us-support.external.hp.com/cki/bin/doc.pl/sid=1615d96002fc771b4b/screen=ckiDisplayDocument?docId=200000015982397&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://us-support.external.hp.com/cki/bin/doc.pl/sid=1615d96002fc771b4b/screen=ckiDisplayDocument?docId=200000058465590" target="_blank"&gt;http://us-support.external.hp.com/cki/bin/doc.pl/sid=1615d96002fc771b4b/screen=ckiDisplayDocument?docId=200000058465590&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://us-support.external.hp.com/cki/bin/doc.pl/sid=1615d96002fc771b4b/screen=ckiDisplayDocument?docId=200000024624577" target="_blank"&gt;http://us-support.external.hp.com/cki/bin/doc.pl/sid=1615d96002fc771b4b/screen=ckiDisplayDocument?docId=200000024624577&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Jan 2002 16:14:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643131#M44229</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2002-01-11T16:14:32Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643132#M44230</link>
      <description>Hi again,&lt;BR /&gt;&lt;BR /&gt;See this also :&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://us-support3.external.hp.com/cki/bin/doc.pl/sid=1930626f016a90f278/screen=ckiDisplayDocument?docId=200000052272641" target="_blank"&gt;http://us-support3.external.hp.com/cki/bin/doc.pl/sid=1930626f016a90f278/screen=ckiDisplayDocument?docId=200000052272641&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Shiju&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Jan 2002 16:15:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643132#M44230</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-01-11T16:15:30Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643133#M44231</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If the dump area does not have the necessary amount of space, then the&lt;BR /&gt;core dump will not contain all of information and, therefore, be less&lt;BR /&gt;useful for analyzing. If the dump device is too small, you will see a&lt;BR /&gt;message similar  on bootup&lt;BR /&gt;Your dump area should be large enough to store the entire contents of&lt;BR /&gt;RAM and the kernel.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;-USA..&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Jan 2002 16:17:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643133#M44231</guid>
      <dc:creator>Uday_S_Ankolekar</dc:creator>
      <dc:date>2002-01-11T16:17:21Z</dc:date>
    </item>
    <item>
      <title>Re: syslog</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643134#M44232</link>
      <description>HPUX will store memory content to the swap file in the event of a system crash. Now that newer systems have gobs of memory, the swap file usually is not made large enough to hold a full crash dump.&lt;BR /&gt;&lt;BR /&gt;I think most administrators ignore this message, since a crash dump is usually not helpful in most crash situations.&lt;BR /&gt;&lt;BR /&gt;-- Rod Hills</description>
      <pubDate>Fri, 11 Jan 2002 16:17:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog/m-p/2643134#M44232</guid>
      <dc:creator>Rodney Hills</dc:creator>
      <dc:date>2002-01-11T16:17:25Z</dc:date>
    </item>
  </channel>
</rss>

