To sumarize, this is a fix for OpenDX on NetBSD not being able
to display really big files despite there being 4GB of RAM. It
works like so:

First I do this to get the limits...

baal: {38}  sysctl proc | grep datasize
proc.curproc.rlimit.datasize.soft = 134217728
proc.curproc.rlimit.datasize.hard = 1073741824
baal: {39}

...So what that means is, my dx process started out with a default
filesize limit of 134217728 but I'm allowed to increase to a
maximum of 1073741824 for whichever process I choose. So next I
find out which process to do it to like so...

baal: {39} ps -xa | grep dxexec
2222 ??  I      0:31.75 /usr/pkg/dx/bin_netbsd/dxexec -r -M1024 -p1 -B
baal: {40}

...Above I asked for the PID of my OpenDX connection to the server, which
is process 2222. Now I will increase its datasize limit to the max
allowed...

baal: {40} sysctl -w proc.2222.rlimit.datasize.soft=1073741824
proc.2222.rlimit.datasize.soft: 134217728 -> 1073741824
baal: {41}

...And violla! Now I can see even my most outrageously large file, the
Belgian Blocks section of an automotive test track as seen by a motor
mount in a prototype car.

Note that since it is a per-process fix, if I close my server connection
in OpenDX the above will need be done again. In due course I'll upgrade
from NetBSD 1.6.2 to NetBSD 2.0 and seek a more enduring fix then. But
for now, at least, this lets me get on with my project.

Thanks to all on the OpenDX and the NetBSD help lists.

Gan

-- 

  Mistera Sturno - Rarest Extinct Bird

  <(+)__       Gan Uesli Starling
   ((__/)=-    Kalamazoo, MI, USA
    `||`
     ++        http://starling.us