Dear Managers,
I can find no way in the Bourne shell to set file-size to
"unlimited" , for a certain user.
ulimit -f unlimited
reports that limit is above that alloweable - presumably
because ulimit -S and ulimit -H confirm that the "soft" and
"hard" limits are the same
**However** if I change the user's shell to the C-shell and
then use the C-shell's "unlimit", I CAN arrive at an unlimited file-size.
(And this is confirmed by a file-copy experiment that used to
fail)
So it is NOT as though I have to muck around with sysconfig
or whatever.
Anybody know the explanation and Bourne-shell trick if there is one ?
Does the C-shell really possess a hook to unlimiting resources that the
Bourne shell doesn't ?
(This issue has really caught us with our pants down, because
the certain user is "oracle" - an Oracle database is started
up by the Bourne shell - we had no idea there was a file-size
limit because we mostly use C-shell's and for some reason this
starts with filesize unlimited. (there's no "unlimit" in either
/etc/csh.login or .cshrc or .login , thats another mystery).
Then our database crashed because a roll-back dbf file exceeded
the max file size, and now we can't restart the db. (That was
another glitch - none of the Oracle dbf's were supposed to be
set up to auto-extend, exactly because of this sort of scenario,
but for some reason this one was))
Am currently setting up an Oracle C-shell environment so we can
try restarting the db with unlimited filesize, but would
really like to nail down whether or not this unlimiting
is possible in the Bourne shell - I have always assumed
that shells did not differ from each other on this sort
of basic-functionality level .
Thanks in advance , I will summarise.
(I know ulimit issues have been raised before but I can't find
exactly this one in the archives)
Alan McCulloch
Bioinformatics Software Engineer
AgResearch NZ
Received on Thu Feb 20 2003 - 08:10:16 NZDT