Now, that it has become possible to have different versions of ooRexx run in parallel (even with different bitnesses), how would one be able to figure out/address the correct rxapi process to be killed? Otherwise after installation the rxapi process continues running (probably until a reboot).
Also with the aim of cleaning out everything known reliably, how would one be able to determine the name and location of the .ooRexx*-lock and -service files, in order to remove them upon uninstall? Maybe a short (external) utility or BIF that would allow to kill that ooRexx version's rxapi and remove its .ooRexx*-lock and -service files may be helpful for cleanup purposes? ---rony _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel