[Grok-dev] grokproject error
uli at gnufix.de
Wed Jan 21 06:46:10 EST 2009
thanks for the backping :-)
Milos Negovanovic wrote:
> On Wed, Jan 21, 2009 at 12:52:11AM +0100, Uli Fouquet wrote:
> > Milos Negovanovic wrote:
> > > (virtualgrok)milosn at mighty grok $ grokproject Sample
> > > /: write failed, file system is full
> > > error: No space left on device
> > > There is plenty of space left on that partition, so i do not know where
> > > is this coming from.
> > The full filesystem here seems to be '/', the root filesystem, not
> > '/home/...' (if they differ). I assume, buildout, setuptools or
> > something else is trying to use /tmp as temporary storage space.
> > You might be able to get around that by setting the 'TMPDIR', 'TEMP', or
> > 'TMP' environment variable to a path inside your home. See
> > http://www.python.org/doc/2.4.3/lib/module-tempfile.html
> > for details.
> Buildout was using /tmp as temporary storage for downloaded files. Doing
> a quick 'rm -rf /tmp && ln -sf /var/tmp /tmp' fixed it.
Although this approach looks rather drastic, we might should mention
this possible error somewhere. Do we have a page with a collection of
all buildout-hassle ever happened to users?
Should we create one? Can the Plone Help Center support us in organizing
it a bit (for instance by categorizing platform-specific,
error-type-specific, blah-specific problems)?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20090121/62ede8e8/attachment.bin
More information about the Grok-dev