Hello Guys, I probably found the problem, why you sometimes have to call halcmd as root to get emc started again. But I don't have a bugfix up to now.
It seems like the complete hal shared memory is not given back to the os when emc is closed and my shm_tester is still running. For that reason you can still access the memory when emc has quit. When halcmd is started from the root account, the memory is also still there, but its possible to start emc again. This is printed after emc has quit: $ halcmd -V status HAL: initializing component 'halcmd26165' HAL: component 'halcmd26165' initialized, ID = 26165 HAL locking status: current lock value 0 (00) HAL_LOCK_NONE - nothing is locked HAL memory status used/total shared memory: 48238/262000 active/recycled components: 1/12 active/recycled pins: 0/417 active/recycled parameters: 0/65 active/recycled aliases: 0/0 active/recycled signals: 36/0 active/recycled functions: 0/17 active/recycled threads: 1/0 HAL: removing component 26165 HAL: component 26165 removed, name = 'halcmd26165' One can also see that there is shared memory left with ipcs: ipcs -m -p | grep <old_pid_of_rtapi_app> Does somebody know, how the rtai version of emc is handling hal shared memory? Is it still there after closing emc? Greetings, Michael ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
