From: Ruby Domalanta (rdomalan@dairy-farm.com.ph)
Date: Mon Oct 06 2003 - 22:23:17 EDT
Many thanks to all who shared their insight. However, these guys gave me the
correct info about the problem.
Robin Slotten
Mike Keighley
Gangadharan Manikandan
To summarize then, the new behavior of ulimit is actually more "correct".
Previously ksh ulimit was set to 4194303 which would rather be translated to
unlimited. Now with the new patch bundles installed the ksh(1) patch has
made it possible to set the value to unlimited instead of 4194303.
The QPK B.11.00.58.5 contains ksh patch PHCO_26783, it fixed the following
ulimit behaviour: 5. ksh ulimit does not report 'unlimited' for filesize.
This causes users to incorrectly assume that ksh
does not handle large files.
The patch corrects the bug of reporting 4194303 instead of unlimited.
Please note that this is only a display problem.
The script running in an Oracle environment setting script (called oraenv),
which contained a command that set the ULIMIT to a specific value:
ulimit 4194304
Since the ksh patch enables ULIMIT to be unlimited, the user script should
be changed to:
ulimit unlimited
The problem with the oracle file "oraenv" can be solve by making the
following change to /usr/local/bin/oraenv
#----------------SNIP------------------#
# Locate "osh" and exec it if found
ULIMIT=`(ulimit) 2>/dev/null`
###################################################
### 7/17/2000 DOTRTS Rob Slotten
### Added the following line to handle $ULIMIT value of unlimited ###
Shifted the rest over 1 tab ### Basically, if $ULIMIT = "unlimited" you
don't have to do anything.
if [ "$ULIMIT" != "unlimited" ] ; then
###################################################
if [ $? = 0 -a "$ULIMIT" -lt 2113674 ] ; then
if [ -f $ORACLE_HOME/bin/osh ] ; then
exec $ORACLE_HOME/bin/osh
else
for D in `echo $PATH | tr : " "`
do
if [ -f $D/osh ] ; then
exec $D/osh
fi
done
fi
fi
fi
#----------------SNIP END------------------#
##########################################
> -----Original Message-----
> From: Ruby Domalanta
> Sent: Sunday, October 05, 2003 1:36 PM
> To: hpux-admin@DutchWorks.nl
> Subject: ksh: unlimited: bad number
>
> Hi Guys,
>
> After I had installed the QPK1100 B.11.00.58.5 on our system, we got these
> ulimit problem on oracle account.
>
> ksh: unlimited: bad number
>
> # ulimit
> unlimited
>
> # ulimit -a
> time(seconds) unlimited
> file(blocks) unlimited
> data(kbytes) 2000000
> stack(kbytes) 8192
> memory(kbytes) unlimited
> coredump(blocks) 4194303
>
> Before, the ulimit setting for oracle account was listed below. Can
> anybody help me explain and help to fix these thing? How can I revert the
> ulimit back to these setting?
>
> # ulimit
> 4194303
>
> # ulimit -a
> ksh: ulimit: bad option(s)
>
>
> Best Regards,
>
> Ruby Domalanta
>
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:35 EDT