On Aug 31, 2004, at 23:29, Sanjay Mishra wrote: Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Men are from Earth. | Women are from Earth. | Deal with it. *--------------------------------------*-------------------------------* _______________________________________________ darwin-development mailing list | darwin-development@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-development Do not post admin requests to the list. They will be ignored. Though daemon works that way ( calling fork() ),but forking fast enough on Mac 10.3.5 seems to slow it down and also the danger of "Resource temporarily unavailable" error message lurks around. I don't understand the above; can you clarify? Do you mean that if you fork 'n' copies of your process, things slow down? There is always a possibility of "resource unavailable". If you are forking with abandon, then you will reach a point where (a) you have too many processes running; or (b) you don't have enough swap space to accommodate them all. This happens on my G4. Am I doing something nasty somewhere? I just fork() and the child created calls execlp(). My main program wait() for the child to end and return with exit(). If you are doing this just once, then I'm unable to explain the symptoms you are seeing. I certainly don't see them, and since the system does just this (fork/exec) for most operations, it's hard to see how it can happen. You must be putting some kind of excessive burden on the system.