<?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 maxdsiz in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz/m-p/2660051#M929028</link>
    <description>Friends, &lt;BR /&gt;&lt;BR /&gt;  What is the maxdsiz equivalent parameter in Solaris ? Please excuse if I have posted it wrong place. Curious to know.&lt;BR /&gt;&lt;BR /&gt;Thank you. &lt;BR /&gt;</description>
    <pubDate>Wed, 06 Feb 2002 18:53:06 GMT</pubDate>
    <dc:creator>Madhu Sudhan_1</dc:creator>
    <dc:date>2002-02-06T18:53:06Z</dc:date>
    <item>
      <title>maxdsiz</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz/m-p/2660051#M929028</link>
      <description>Friends, &lt;BR /&gt;&lt;BR /&gt;  What is the maxdsiz equivalent parameter in Solaris ? Please excuse if I have posted it wrong place. Curious to know.&lt;BR /&gt;&lt;BR /&gt;Thank you. &lt;BR /&gt;</description>
      <pubDate>Wed, 06 Feb 2002 18:53:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz/m-p/2660051#M929028</guid>
      <dc:creator>Madhu Sudhan_1</dc:creator>
      <dc:date>2002-02-06T18:53:06Z</dc:date>
    </item>
    <item>
      <title>Re: maxdsiz</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz/m-p/2660052#M929029</link>
      <description>Allen,&lt;BR /&gt;&lt;BR /&gt;I'm not sure there is a DOCUMENTED direct relationship, but:&lt;BR /&gt;&lt;BR /&gt;There is often a need to change the default har d and soft limit values. Sometimes the maximums need to be r educed to keep processes from hogging the system and sometimes the default number of files needs to be incr eased. Rather than setting limits in every user login script the global default limits in the kernel can be changed. In generic Unix System V Release 4 this is performed by setting some symbolic variables and r ebuilding the kernel. In Solaris 2 the /etc/system method cannot be used since there are no variables corresponding to the individual limits, just a single rlimits data str ucture. The kernel must be patched using adb. The elements ar e laid out as shown by the sysdef -i command, which shows the values in hexadecimal. &lt;BR /&gt;&lt;BR /&gt;To increase the default number of file descriptors per pr ocess rlimits+28 must be patched with adb as shown below . &lt;BR /&gt;&lt;BR /&gt;The commands shown below permanently patch the default number of file descriptors to 128 (0x80) in the /kernel/unix file using "?" and also patch the current copy in memory using "/". &lt;BR /&gt;&lt;BR /&gt;Soft:Hard Resource byte offset in hex Infinity:Infinity cpu time 0: 4 Infinity:Infinity file size 8: c 1fefe000:1fefe000 heap size 10:14 800000: ff00000 stack size 18:1c Infinity:Infinity core file size 20:24 40: 400 file descriptors 28:2c Infinity:Infinity mapped memory 30:34 &lt;BR /&gt;&lt;BR /&gt;# cp /kernel/unix /kernel/unix.orig # adb -k -w /kernel/unix /dev/mem rlimits,e?X rlimits: rlimits: 7fffffff 7fffffff 7fffffff 7fffffff 1fefe000 1fefe000 800000 ff00000 7fffffff 7fffffff 40 400 7fffffff 7fffffff &lt;BR /&gt;&lt;BR /&gt;Warning - using adb to patch the kernel dir ectly is a potentially danger ous operation. Mistyping a command could crash the system or r ender it unbootable. Save an unpatched kernel copy . Do not incr ease the hard limits. &lt;BR /&gt;&lt;BR /&gt;Buffer Sizes And Tuning Variables 49 &lt;BR /&gt;&lt;BR /&gt;from:&lt;BR /&gt; &lt;A href="http://www.cs.ualberta.ca/operations/Doc/Sun-Tuning/SunPerfOvDec93.ps.gz" target="_blank"&gt;http://www.cs.ualberta.ca/operations/Doc/Sun-Tuning/SunPerfOvDec93.ps.gz&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;in Solaris, it's the HEAP (datasize in ulimit). Using the mapping above you can change it - good luck!!!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Wed, 06 Feb 2002 21:43:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz/m-p/2660052#M929029</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-02-06T21:43:23Z</dc:date>
    </item>
    <item>
      <title>Re: maxdsiz</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz/m-p/2660053#M929030</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I agree with Harry.&lt;BR /&gt;&lt;BR /&gt;In Solaris, using ulimit with the -d option sets the maximum size of a process's data segment eg. &lt;BR /&gt;&lt;BR /&gt;# ulimit -d 65536&lt;BR /&gt;&lt;BR /&gt;This sets the process's maximum data segment size to 64 MB.&lt;BR /&gt;&lt;BR /&gt;Hope this helps. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong</description>
      <pubDate>Thu, 07 Feb 2002 03:09:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz/m-p/2660053#M929030</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2002-02-07T03:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: maxdsiz</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz/m-p/2660054#M929031</link>
      <description>Great response Harry !  Thanks a lot. &lt;BR /&gt;Allen.</description>
      <pubDate>Thu, 07 Feb 2002 11:30:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz/m-p/2660054#M929031</guid>
      <dc:creator>Madhu Sudhan_1</dc:creator>
      <dc:date>2002-02-07T11:30:32Z</dc:date>
    </item>
    <item>
      <title>Re: maxdsiz</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz/m-p/2660055#M929032</link>
      <description>Allen,&lt;BR /&gt;&lt;BR /&gt;I spent at least three hours on that one. I have a sparky-ultra5 on my desk (that I use about twice a month), and I even asked my consultant and they had no clue. But it was time well spent, because I believe that Hp approached the issue correctly by making this a true kernel parameter. I don't want some rogue runaway program consuming memory like candy. If I have a need, and I have, I jack maxdsiz up, but only based upon need not greed :-))&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry</description>
      <pubDate>Thu, 07 Feb 2002 12:01:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/maxdsiz/m-p/2660055#M929032</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-02-07T12:01:28Z</dc:date>
    </item>
  </channel>
</rss>

