Bug#696417: may well be unrelated

[Graeme Vetterlein <graeme@vetterlein.com>]

... but in case other folks get here , due to google matches.

I suspect the reason CUPS was reporting  these messages and failing (and 
also testprnt was failing)
was lack of real memory. The print sever is running on a DreamPlug , 
without swap and I think it was
running out f real memory.

Clue was , when restarting cups I was  getting "cannot fork"  type 
message (for KID3)  and it really looked like fork(2)
was failing ... ulimit was high ... so my guess was resource consumption 
... e.g. memeory.

--

I guess some better log entries would help ... if that is what is 
happening during normal print (not restart)

--

Graeme