Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!decvax!decwrl!sun!texsun!smu!trsvax!authorplaceholder
From: gm@trsvax.UUCP
Newsgroups: comp.unix.xenix
Subject: Re: ulimit in XENIX
Message-ID: <196500003@trsvax>
Date: Mon, 18-May-87 15:49:00 EDT
Article-I.D.: trsvax.196500003
Posted: Mon May 18 15:49:00 1987
Date-Received: Sat, 23-May-87 19:22:32 EDT
References: <517@elandes.UUCP>
Lines: 35
Nf-ID: #R:elandes.UUCP:517:trsvax:196500003:000:1482
Nf-From: trsvax.UUCP!gm    May 18 14:49:00 1987


As in another response, you can set the ULIMIT in /etc/default/login.
However, there are some Xenix's that do not support a large ULIMIT.

I know that the older IBM and SCO /etc/login's will not accept a 
ULIMIT larger than 32767. Some Xenix's will support larger, but the
login program will say "Could not set ULIMIT", even though the ULIMIT
was indeed set.

I complained about this during the Tandy release of Xenix. On Tandy Xenix,
you can set ULIMIT to a value larger than 32767 without anybody 
complaining. I personally have tested it up to ULIMIT=100000.

Warning to those people running an older 286 Xenix: If you have a file 
larger than 33MB, and you do a "cp filename bigfile" or you have any 
program which does a `fopen(bigfile, "w")', the system will trash your 
free list.  There is a bug in older Xenix kernels in the itrunc() routine
which loses track of the disk space above the 33MB limit. Anything
that calls unlink(), such as "rm" will work fine. 

One way to test this would be to set your ULIMIT above 32767, mount a 
floppy and do a:

	dd if=/.profile of=bigfile seek=63b

This will create a 33.6MB file on your floppy (!) with a huge hole in it. 
Now copy a smaller file on top of bigfile, umount the floppy and do a fsck 
of it.  If your kernel has the bug, you will wind up with several hundred 
blocks missing from the free list.


						-gm@trsvax.UUCP

			"I hear he checks his sanity with a stopwatch."
				"What do you check yours with, a dipstick?"