Ulimit on V/68 (Was: Re: B News 2.11 forgeting artciles)

[Kent Forschmiedt]

 [Chris Lewis is running B News 2.11 Patchlevel 14, running on V/68 
  R2V?; it breaks its history file;  David Beckemeyer suggests that the 
  problem is ulimit, then suggests putting a large ulimit in the 
  crontab line.] 

Since V/68 R2 has private crontabs, and Lewis' news is hopefully not 
running as root, a ulimit command in the crontab won't work.  Happym is 
running V/68 R2V2.3, and the default ulimit is 1MByte.  Rather silly.  
Fortunately, V/68 includes MAXULIMIT in its tunable parameters. Here is 
how you fix it (this doesn't require source, only the standard link kit 
- you have it unless you deleted it): 

$ su
# cd /usr/src/uts/m68k
# ed cf/cmaster
/MAXULIM/s/[0-9]*$/32768/
w
q
# make vme131_?  # see below...

There are several configurations, vme131_[1-n], depending on when you
bought your system and things.  The differences are mainly which drivers
are included and how many devices to make space for in the disk and
serial port drivers.  If you are running an off the shelf configuration,
it is probably 1 [40M drive(s)], 2 [40M drives plus SMD device], 3 [70M
drive(s)], or 6 [70M + SMD].  There is a line in each kernel's commands
something like this:

		DFOPTS="-DM320DK0=WD70 -DM320DK1=WD70 -DM320DK4=WD70
		 -DM320DK5=WD70 -DM320=2 -DM350=1 -DDBUF=1 -DCNFIG=3"

This one says that disks 0, 1, 4 and 5 are 70M winchesters, there are 2 
MVME320 disk controllers, 1 MVME350 tape controller, and some other 
things you probably shouldn't mess with.  The SMD controller is MVME360,
so if you have one you should choose a configuration with -DM360=1 in it.

There are lots of other things that you can tweak, although some of them
are dangerous.  You probably will want to increase MAXPMEM if you have
more than 2M of RAM in your system.
-- 
 kent at happym.wa.com, uunet!nwnexus!happym!kent, Happy Man Corp 206-282-9598