+-------[ Christopher N. Deckard ]----------------------
| -----BEGIN PGP SIGNED MESSAGE-----
| Hash: SHA1
| 
| On 1/7/10 2:39 PM, Andrew Milton wrote:
| > +-------[ Christopher N. Deckard ]----------------------
| > | -----BEGIN PGP SIGNED MESSAGE-----
| > | Hash: SHA1
| > | 
| > | On 1/7/10 2:30 PM, Andrew Milton wrote:
| > | > +-------[ Brian Brinegar ]----------------------
| > | > | I'm fairly well versed on the inner workings of Zope, but yesterday 
I've
| > | > | run into a problem that I can grasp.
| > | > 
| > | > [snip]
| > | > 
| > | > | Anyway, here's what I see. The copy starts, a tempfile is created (on
| > | > | the client) and grows to the appropriate size (3.1GB). Then, a
| > | > | Data.fs.temp appears on the new server and grows to the appropriate
| > | > | size. However, when my script tries to commit the transaction I get an
| > | > | EOF error:
| > | > 
| > | > File size limits on the new server restricting to say 2GB?
| > | 
| > | No.  It's an x86-64 RedHat 5 install.  We've had 250GB files on this 
system.
| > 
| > Got any errors in your ZEO log ?
| 
| Aha!  Our zeo log shows that we are running out of space in /tmp.  What
| is the best way to redefine the location for temp files for the ZEO server?

Set the TMPDIR env var to point to where you want tmp files created in
the shell script that starts your ZEO server

-- 
Andrew Milton
a...@theinternet.com.au
_______________________________________________
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to