My 10.3.8 OS X Server have 0 available on / but had no errors in the console log.
Ran like a dog (expectedly!).
Deleted a 5MB tar file and a 45GB /var/adm/log/system.log (45GB).
No disk full error here.
Dobby.
It's real strange. I had a job running all night, and I just want to pinpoint at what stage the thing ran out of memory, because surprisingly the thing finished and on first glance everything looks ok, but then I can't explain why I had 0kb available...
I got the disk full message which I haven't deactivated...it was on screen when I woke up. I closed it, expecting the job to be half-baked.
Comments
My 10.3.8 OS X Server have 0 available on / but had no errors in the console log.
Ran like a dog (expectedly!).
Deleted a 5MB tar file and a 45GB /var/adm/log/system.log (45GB).
No disk full error here.
Dobby.
Originally posted by dobby
You might get a disk full message.
My 10.3.8 OS X Server have 0 available on / but had no errors in the console log.
Ran like a dog (expectedly!).
Deleted a 5MB tar file and a 45GB /var/adm/log/system.log (45GB).
No disk full error here.
Dobby.
It's real strange. I had a job running all night, and I just want to pinpoint at what stage the thing ran out of memory, because surprisingly the thing finished and on first glance everything looks ok, but then I can't explain why I had 0kb available...
I got the disk full message which I haven't deactivated...it was on screen when I woke up. I closed it, expecting the job to be half-baked.
--B