ujpper file size limit
Chaz
I work predominantly with SCO UnixWare.
This OS has a limitation that I may not be able to get over.
The problem is that UW will handle file sizes up to 1 terrabyte in
size, for interrogation and manipulation, but will not handle files
above 2Gb when added to or created using shell redirection.
This limit is stipulated in SCO Knowledge base technical article 110169
The reason I require this is because the software I support uses c-isam
database, which has data and index files that are "added" to all the
time.
What I am looking for is a UNIX flavour that will allow shell
redirection out to a much larger file size.
Does anybody have any ideas?
Cheers,
Chaz.
Steve James
Can you write a simple utility to read from stdin and write to the large
file, then pipe the output to your utility instead of simply redirecting the
output to the file? A little ugly, I know, but a simple workaround if it
would work for you. Something like...
lfs-output-program | lfs-writer-program -o lfs-output-file
instead of...
lfs-output-program > lfs-output-file
Would that work?
Steve J.
John Schmidt
> The problem is that UW will handle file sizes up to 1 terrabyte in
> size, for interrogation and manipulation, but will not handle files
> above 2Gb when added to or created using shell redirection.
Can't you get an updated version of your shell of choice that's
largefile aware?
JS
Chaz
A bit of food for thought there.
It seems that my main problem is that UW7 only supports a 32 bit
interface,(2 x 2 to the power of 32 = 2Gb). If I could get my hands
round an OS that supports 64 bit, then the world is my oyster.
Good point on the updated shell bit there John. Our application uses
ksh, which having performed all the fsadm bits and the kernel tuning
allows 1 terrrabyte, but the maximum file size for shell redirection is
still governed by the maximum allowable value of the ULIMIT parameter
in /etc/default/login
I'd love to just go all Linux, cos bash seems to be more manly, but my
company has agreements with SCO, and we all know what is going on
there, don't we.......
Thanks again,
Chaz.
Steve James
714 with LFS support has file sizes using more than 32 bits, up to 1 TB...
http://uw714doc.sco.com/en/man/html.2/Intro.2.html#LargeFileSupport
If an updated shell can do what you need, then a program could do it and
could probably get it done more easily and quickly, though admittedly not as
cleanly. The 1TB limit may not be enough for what you need, but since that
is a UW O/S limitation, I would expect it to apply to any enhanced shell as
well.
Steve J.
-----Original Message-----
From: Jean-Pierre Radley [mailto:ne...@jpr.com]On Behalf Of Chaz
Bill Vermillion
>It seems that my main problem is that UW7 only supports a 32 bit
>interface,(2 x 2 to the power of 32 = 2Gb). If I could get my hands
>round an OS that supports 64 bit, then the world is my oyster.
>Good point on the updated shell bit there John. Our application uses
>ksh, which having performed all the fsadm bits and the kernel tuning
>allows 1 terrrabyte, but the maximum file size for shell redirection is
>still governed by the maximum allowable value of the ULIMIT parameter
>in /etc/default/login
That reminds me of a problem on an old AT&T 3B310 I had years ago.
They had a ULIMIT set obscenely low in login, and only root could
up ULIMIT, so users were stuck.
The answer was to compile a short C program that set the ULMIT to
a more reasonable amount, move the orignal login to login2, and
have the new program be named 'login' which then called login2 with
the new ULIMIT.
The /etc/default/login will only allow you to lower the ULIMIT from
the maxium.
>I'd love to just go all Linux, cos bash seems to be more manly, but my
>company has agreements with SCO, and we all know what is going on
>there, don't we.......
bash may be 'more manly' but to me it does stupid things. I've
moved to a KSH environment in the mid-90s, and have never had a
problem, though bash often seems to be a moving target.
Bill
--
Bill Vermillion - bv @ wjv . com