<?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: uling ulimit command in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/uling-ulimit-command/m-p/5006261#M425593</link>
    <description>How is it not working?  What is happening?&lt;BR /&gt;&lt;BR /&gt;As to usage have a look at the man pages for the shells.&lt;BR /&gt;&lt;BR /&gt;# man sh-posix&lt;BR /&gt;&lt;BR /&gt;# man ksh</description>
    <pubDate>Sun, 01 Oct 2006 13:26:56 GMT</pubDate>
    <dc:creator>Patrick Wallek</dc:creator>
    <dc:date>2006-10-01T13:26:56Z</dc:date>
    <item>
      <title>uling ulimit command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/uling-ulimit-command/m-p/5006260#M425592</link>
      <description>I have client trying to set ulimit witin there application. I there a different command structure between ksh &amp;amp; sh ?? they are using: ulimit -n 8000 and they say it isn't working ??</description>
      <pubDate>Sun, 01 Oct 2006 13:05:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/uling-ulimit-command/m-p/5006260#M425592</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2006-10-01T13:05:23Z</dc:date>
    </item>
    <item>
      <title>Re: uling ulimit command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/uling-ulimit-command/m-p/5006261#M425593</link>
      <description>How is it not working?  What is happening?&lt;BR /&gt;&lt;BR /&gt;As to usage have a look at the man pages for the shells.&lt;BR /&gt;&lt;BR /&gt;# man sh-posix&lt;BR /&gt;&lt;BR /&gt;# man ksh</description>
      <pubDate>Sun, 01 Oct 2006 13:26:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/uling-ulimit-command/m-p/5006261#M425593</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2006-10-01T13:26:56Z</dc:date>
    </item>
    <item>
      <title>Re: uling ulimit command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/uling-ulimit-command/m-p/5006262#M425594</link>
      <description>Thanks, the problem was there application was executing a script that was setting the ulimit to 2048. Later on the application was executing another script that was trying to set the limit higher and failing. Problem being that once ulimit is set it can't be raised higher.</description>
      <pubDate>Sun, 01 Oct 2006 14:28:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/uling-ulimit-command/m-p/5006262#M425594</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2006-10-01T14:28:46Z</dc:date>
    </item>
    <item>
      <title>Re: uling ulimit command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/uling-ulimit-command/m-p/5006263#M425595</link>
      <description>Actually, not quite correct. ulimit can set values higher and lower but the -S option must be used. ulimit -Sn 2048 can be raised at a later time. Tell the client to add -S to all changes to ulimit. Note also that ksh ulimit was just recently enhanced. ulimit -a shows all settable values in the POSIX sh shell. Older (unpatched) versions of ksh had only one option - ulimit -a would return an error.</description>
      <pubDate>Sun, 01 Oct 2006 15:34:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/uling-ulimit-command/m-p/5006263#M425595</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2006-10-01T15:34:11Z</dc:date>
    </item>
  </channel>
</rss>

