Thanks Ernie --

I'm going to go through the documentation for the Service Management framework 
and see what I can come up with. I was hoping I wouldn't need to maintain two 
separate code bases for MacRuby and MRI but  if i can launch processes without 
reverting to a hack it's always a good thing.

Thanks,
Rob
On 17 Feb 2010, at 15:45, Ernest N. Prabhakar, Ph.D. wrote:

> The recommendation is to use launchd to spawn processes via Service 
> Management:
> 
> http://developer.apple.com/mac/library/documentation/General/Reference/ServiceManagementFwRef/ServiceManagement_h/index.html
> 
> But I don't think anybody has wrapped it yet...
> 
> -- Ernie P.
> 
> On Feb 17, 2010, at 5:42 AM, robert gleeson wrote:
> 
>> Hi --
>> 
>> I'm aware fork() is not implemented in MacRuby yet, and it may never be from 
>> what I read but I'd just like to introduce a use case i've come across 
>> recently that might have you reconsider?
>> 
>> I am writing ruby bindings for the features exposed in the "sandbox" header, 
>> and you really need to fork a process if you don't want your parent process 
>> to inherit the restrictions the sandbox imposes .. 
>> 
>> I came across the problem with CoreFoundation not allowing you to fork() 
>> without immediately executing exec() , and I presume this is one of the 
>> reasons fork() in MacRuby might not be implemented but is there any 
>> workaround to see fork() being implemented? 
>> 
>> Just thought I'd add that to the table.
>> 
>> Thanks,
>> Rob
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Reply via email to