Mac throws "Can't fork" after forking daemon a number of times. W hats wrong ?
Mac throws "Can't fork" after forking daemon a number of times. W hats wrong ?
- Subject: Mac throws "Can't fork" after forking daemon a number of times. W hats wrong ?
- From: Sanjay Mishra <email@hidden>
- Date: Wed, 7 Jul 2004 16:08:30 +0530
Hi,
I have written a CUPS filter on Mac (Panther) and it is working fine on
dual processor machines but on single processor Mac the OS throws an error
"Can't fork" after around 80 transactions. Only when I am using my filter
this message is thrown.I am not doing much in my filter.I just pass all the
arguments to it to one of the existing filters using execlp() and call
wait() as the last function in the filter.
My application has many parts. One of them process the HTTP request. The
other is the CUPS filter. The third which converts the document requested in
the PDF format. Hence the sequence is that when the application receives the
HTTP request for sending a file across it gets the file from a predefined
location and converts it into PDF format (during this the CUPS filter gets
called by the OS) and is sent across the network to the client. After around
80 transactions and that too only on the single processor Mac machines it
throws the error "can't fork".
What could be going wrong? Where I should start looking into ? I looked at
the number of files my application opens and it is closing all of them at
the proper place. Are there any tool that can help me out.
Where ever I am forking I made sure that it does not hang and closes
properly. I tested them.No error is thrown if I am running the application
on dual processor system.
Regards,
Sanjay Mishra
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.