Sure. I have done this on more that one occasion. I have several shipping
using tfork() in a configuration similar to what you describe. There seems
to be a lot
of misunderstanding about tfork(). Just think of tfork() as two processes
never used it for more that two processes), where the shared memory is
setup for you, and it just happens to be your regular old data segment.
Anything that you would do with two processes, and shared memory, can be
tfork() (and vise-versa), and there is a less coding involved. It is not a
model but it is a convenient construct, that can be used to good effect for
narrow range of problems (what you describe sounds like it fits into this
“Tom Stave” <email@example.com> wrote in message
I am looking at using tfork() in a QNX4 application. My created child
(thread) will only be using the following library functions:
Does any know if I would be safe in using tfork(). I don’t know if any of
these functions are thread safe in QNX4.