Unix 5.4 and ulimit
Bruce D. Becker
bdb at becker.UUCP
Sun Apr 28 19:04:53 AEST 1991
In article <dcm.672428949 at baldur> dcm at baldur.dell.com (Dave McCracken) writes:
|scotte at applix.com (Scott Evernden) writes:
|
|>In article <1991Apr21.140740.6766 at gold.sub.org> root at gold.sub.org (Christian Seyb) writes:
|>>Hello,
|>>
|>>I am using Unix 5.4 (4.0.2) and have a problem with ulimit.
|
|>Upping your ulimit is described in the FAQ for this group. I quote: "
|> 1. If your desired limit is > 12288(6MB):
|> Edit /etc/conf/cf.d/mtune to change the following line:
|> ULIMIT 3072 2048 12288
|> to:
|> ULIMIT 3072 2048 xxxxx
|> etc.
|
|Unfortunately, this is no longer accurate for Unix 5.4 (SVR4).
|The files that need to be changed are still valid
|(/etc/conf/cf.d/?(mtune|stune)), but the value that controls
Where will one find these files in the
System V release 4 version for the Amiga?
|file size limit (nee ULIMIT) has changed. As of SVR4, the complete
|BSD-style resource limit capability has been implemented. To
|change what is commonly considered ULIMIT, you need to change
|the entries SFSZLIM (for soft limit) and HFSZLIM (for hard limit).
|They are close to the bottom of the mtune file, along with some
|comments (!!) that describe what they are. These limits are in
|bytes, rather than blocks, and a value of 0 is no longer used
|to mean unlimited. Unlimited is now MAXINT.
|
|Note that the ULIMIT entry in /etc/default login should still
|work, and the shells still understand the ulimit command. For
|a quick peek at the new features, to a "ulimit -A" to ksh.
|Unfortunately, the values are printed in blocks for compatibility,
|so be prepared for some confusion.
That seems to be "ulimit -a" here...
--
,u, Bruce Becker Toronto, Ontario
a /i/ Internet: bdb at becker.UUCP, bruce at gpu.utcs.toronto.edu
`\o\-e UUCP: ...!utai!mnetor!becker!bdb
_< /_ "The really important problems require greater earnestness" - J. Cage
More information about the Comp.bugs.sys5
mailing list