Hi all, I am having some difficulties using the mknod() function to create named pipes. I am currently porting an OMX Resource Manager which relies heavily on intra-process communication.
I was wondering if there are any differences in the mknod() used in Android vs. the standard implementation? Also, in this same component I have been appending the PID (obtained from getpid()) to the named pipe's name. For example "/dev/ pipename_790" is created. I create one of these pipes for each other registered component in the system. It appears that this is causing some problems and I have noticed that the same PID is being used for each component. Can someone describe how process are started and which tasks will get different PID's in the Android environment? Another interesting point is that I can create pipes using simple names, i.e. only the pipes with the PID appended fail to be created... Any info will be helpful! Thanks, Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
