I take back what I said about the process no longer being running. If the app crashes or you force quit the app processes started in either ShellMBS or NSTaskMBS are left running. Thats why I can’t re-open the ports. They no longer show as a child process of the parent program of course since the parent program is no longer there, but the programs are still there. Should not any child processes be killed when the parent process is? Do I need to do something special to make that work? Or should that be part of the implementation?
> On Nov 18, 2020, at 9:45 AM, ja...@sentman.com wrote: > > I’ve re-implemented the app using an NSTaskMBS rather than the ShellMBS and > it does the same thing. If I force quit the child processes everything is > fine. They release their sockets. If I force quit the parent app then any > ports they had listening are no longer available until the machine restarts. > Do these shells not get the proper signals passed through if the parent > process receives a signal? Is that something I need to do manually in a > signal handler? Can I even do that if my app crashes or is force quit? I’m > not sure what to do about that yet but will keep futzing around ;) > Thanks, James James Sentman http://www.PlanetaryGear.org http://MacHomeAutomation.com _______________________________________________ mbsplugins@monkeybreadsoftware.info mailing list %(list_address)s https://ml-cgn08.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
