[typo] is r1303 unstable for others, too?
urban at bettong.net
Fri Dec 22 09:56:08 EST 2006
-----BEGIN PGP SIGNED MESSAGE-----
On Dec 12, 2006, at 0:32 , Piers Cawley wrote:
> So, what do we know?
> 1. Migrations went smoothly and you're on schema version 61
> 2. Textdrive isn't killing stuff because it's not putting any reports
> in your home directory
> 3. Typo's dying before it logs anything.
4. Sometimes I get the message "[FATAL] failed to allocate memory" on
the console that I started the FCGI on. BTW, maybe it's of interest: I'm
running Typo as an FCGI process using lighttpd. I mean, I start the FCGI
using "spawn-fcgi" and tell lighttpd where to find the socket.
> Does it always die in the same place?
Not really. It seems that the problem occurs whenever Typo tries to load
a new page that isn't in the cache, yet. Sometimes it works for a page
more, but once I try to load another page that isn't in the cache (or so
I'm guessing) it blows up.
http://bettong.net - Urban's Blog
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
-----END PGP SIGNATURE-----
More information about the Typo-list