The command "ulimit -a" reveals :
time(seconds) unlimited
file(blocks) 2097151
data(kbytes) 131072
stack(kbytes) 32768
memory(kbytes) 32768
coredump(blocks) 2097151
nofiles(descriptors) 2000
Any suggestions for corrective action would be welcome.
Try 'df' - it looks as if you have a full disk.
Regards,
Nick Maclaren,
University of Cambridge Computing Service,
New Museums Site, Pembroke Street, Cambridge CB2 3QH, England.
Email: nm...@cam.ac.uk
Tel.: +44 1223 334761 Fax: +44 1223 334679
look if there is a process that fills /tmp (maybe cron)
dav a écrit dans le message ...
Your /home filesystem is full. Every command is logged by ksh in
~/.sh_history and
you can't write to it since home is full.
df is your friend.
Norm
I concur with fhr's response. your /tmp filesystem is probably full.
First, look for any tmp files and remove them. If you have room you
can increase the space with the command:
chfs -a size=+100 /tmp
and it will increase to the next rounded increment. You can then
scroll through and get rid of anything not needed (by you - not the
system).
Bob
I've also seen this message when the root directory has filled up.
Unexpectedly large files (such as core files) can sometimes set this
up accidently.
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Jim Lahue | Disclaimer: All expressed
jml...@us.ibm.com | views are mine alone and not
Server Group, IBM Corp. | necessarily shared by IBM
--
Nick Maclaren <nm...@cus.cam.ac.uk> wrote in message
news:a6ptks$qa5$1...@pegasus.csx.cam.ac.uk...
Exactly. Note that this does not usually prevent the command from
executing, it just won't get logged.
--
Gary R. Hook / AIX PartnerWorld for Developers / These opinions are MINE
________________________________________________________________________